Project Management Lessons Learnt

Big Data is a huge area .For those of you, who have already ready many literatures and now implementing it in your projects or product, this article may be worthy of skimming only. For others who are to yet to read something on Big Data and are interested. I hope this article gives  basic information and context and prompts you to explore the fascinating area of Big Data Analytics. What's Big Data? Big Data can be thought of a solution platform and ecosystem that address the problem of unavailability of a fast, interactive, accurate, and cost effective analytics that can work on humongous amount of structured, unstructured varied data both offline or at real time. Big in   Big Data essentially not only refers to the humongous volume of data set but refers to something which is difficult to manage and calls of out of the box solutions. What are the characteristics of Big Data? The characteristics of Big Data helps to better understand i...

During release cycles and delivery..it's important to review and if needed group all stakeholders and have a workshop to discuss, brainstorm , review and firm up delivery plan and get things moving, pick up pace in release.In this post, will touch upon certain aspects and pen some thoughts towards having a successful stakeholder's workshop. Why a workshop.. Over a period of time as release progresses and due to changes it keeps on dragging and priorities change..a review indicates that we have few items which need decision..few items which are strategic and need deliberations...there is a pressing need that all stakeholders are on the same page and the release details needs updates ..to realize the road map are detailed and agreed by all..and may be the road map itself needs a revisit..may be need a break  from continuous operations and retrospect.. try to look at issues/challenges and encourage some out of the box thinking...agree and get the release done. It may be more n...

Hi..saw a recuritment ad..thought of mentioning it..nice to remind always if we  are executing all responsibilites daily and proactively...Will try to augment the list with more thought..  Prepare/Review project plan and schedule.Keep it updated at all times.  Project monitoring and control to ensure delivery as per project scope, schedule and quality  Ensure Requirements/Use Cases are detailed/reviewed and understood by Dev and Test Teams.   Accurate and Appropiate Status reporting to client / management as per Project Communications Plan..  Risk management and issue management  Change management , Configuration management ,Measurement and analysis   Adherence of coding standards ,Process compliance..Automated Build/Deployment..Continous Integration..SVN hygine...Junits..Code Violations w.r.t standards,functionality,security,performance,and IP are checked at developer's desk and doesn't land up in trunk for discovery during later phases o...

Hi..Today evening,,got an opportunity to hear some tips from a senior IT manager who had worked for 29 years in IT projects..He shared few things he says often he shares with his son who is also now in IT to bear in mind: Accept the facts that requirements in an IT projects will definitely change..so fundamental acceptance of this fact by you/your team will help one to deal things better.He suggested to take effort and have customer accept the fact.He broadly advocated the agile delivery paradigm..and encouraged to actively get the buy-in to deliver in iteration-1 current understanding of requirements and then in subsequent iterations..the next set of requirements..i.e have the mechanism in place like agile delivery advocates and work in sprints..so that if a new set of requirements are available..the next sprint can handle it.Always keep Customer as your first responsibility. Have the humility to accept mistakes..as the option of hiding it is just temporary and has greater adverse...