Wednesday, 1 April 2015

Agile Software Project Management Methodologies 



Successfully project planning, coordinating and controlling in order to deal effectively with projects sponsors, customers, unexpected risks and changing scope are difficult tasks even for the most experienced project managers. Different surveys indicated that about half of the software projects were considered total failures and only a few of them were successful. The tight deadlines, volatile requirements and emerging technologies are the main reasons for this lake of performance. This agile project environment requires an agile project management. The main characteristics of the agile software project management approaches are: MSF for Agile Software Development, Extreme Programming, Scrum, Crystal, Feature Driven Development, DSDM. 


The agile approach started in 1994 with some trials of semi-formal agile methodologies, such as RAD, DSDM, XP, Crystal, Scrum. These methodologies are based on agile methods. Agile methods are adaptive rather than predictive. Engineering methods tend to try to plan out a large part of the software process in great detail for a long span of time, this works well until things change. So their nature is to resist change. The agile methods, however, are waiting for change. Agile methods are people-oriented rather than process-oriented. The goal of engineering methods is to define a process that will work well whoever happens to be using it. Agile methods assert that no process will ever make up the skill of the development team, so the role of a process is to support the development team in their work.
The declaration of principles and values in the agile approach is known as the Agile Software Development Manifesto, launched in 2001, after a two day workshop at Snowbird Utah (figure 3). A non-profit organization the Agile Alliance was set up to promote knowledge and discussion of all the agile methods. Applying these principles creates the foundation for managing IT projects in an agile approach. The basic characteristics of this approach are the following:
 • Assume simplicity. As the project evolves it should be assumed that the simplest solution is the best solution. Overbuilding the system or any artifact of the project must be avoided. 
• Embrace change. Since The stakeholder understanding of the requirements will change over time. Project stakeholders themselves may change as the project makes progress. Project stakeholders may change their point of view, which in turn will change the goals and success criteria of the project management effort.  
• Incremental change – the pressure to get it right the first time can overwhelm the best project manager. Instead of futilely trying to develop an all encompassing project plan from the start, put a stake in the ground by developing a small portion of the system, or even a high–level model of a larger portion of the system, and evolves this portion over time. Or simply discard it when you no longer need it in an incremental manner.
 • Maximize stakeholder value. The project stakeholders are investing resources (time, money, facilities) to have a system deployed that meets their needs. Stakeholders expect that their investment to be applied in the best way. 
• Manage with a purpose Identify a valid purpose for creating the artifact and the audience for that artifact. This principle also applies to a change to existing artifacts.
 • Rapid feedback. The time between an action and the feedback on that action must be minimized. Work closely with the stakeholders, to understand the requirements, to analyze those requirements, and develop an actionable plan, which provides numerous opportunities for feedback. 
• Working software is the primary goal of the project. The goal of any software project is to produce software that meets the needs of the project stakeholders. The goal is not to produce extraneous documentation, management artifacts or models of these artifacts. 

No comments:

Post a Comment