Agile has not only reinforced the interest in project management but also challenged the conventional idea of such management. It focuses on project management institutions where it is difficult to plan ahead with mechanisms for emprical process control, such as where feedback loops constitute the core element of product development to traditional command-and-control- oriented management. It represents a radically new approach for planning and managing requirements a.k.a backlog management, bringing decision-making authority to the level of operation properties and certainites.
The toughest job is encountered in the maintenance phase which normally accounts for the highest amount of money. The maintenance team is decided such that they monitor on the change in organization of the software and report to the developers, in case a need arises.
Have you been struggling to understand which tool do you engage within your organization to manage Agile development. Have you ever been put into a situation where you followed an agile tool but never liked it. I guess this situation sounds familiar atleast to half of us. In my experience i have come across many organizations where an agile tool is rolled out may be due to the reason that someone from Senior Management was impressed and have asked us to follow.
There are big questions often asked when an organization plans to transition to agile from any traditional development methodology. Are project managers required for agile projects? Is there a role for PMO within agile environment? And like....
While this article does not address these questions, it certainly provides a view into common issues across organization following agile and role of PMO to address these issues. Let me start by saying PMO is absolutely required for an agile project/programme environment.
Talk about integrating code to any developer and it seems to be the most painful activity of whole development lifecycle. We, the developer community tend to integrate our code once we are happy that all development is complete, tested and about to release the source to production....there you go loads of issues post integration due to either lack of complete knowledge on code being integrated or integrated code not tested properly and many others.
This article is just an attempt to introduce Scrum, based on my personal experience working in agile environment in simple terms. Probably would be a good guide to someone who has some know how on agile and like to have a clear picture on what shall scrum by definition contain.