| 5 Oct 2014
Traditional project management involves disciplined and deliberate planning as well as control methods. With this approach, we can easily recognize distinct project lifecycle phases. Tasks are completed one after another in an orderly sequence – this demands that a vital part of the project be planned upfront. In addition, with traditional project management, once a phase is complete, it is assumed that it will not be revisited.
Agile project management is a highly iterative and incremental process, where developers and project stakeholders actively work together to understand the domain; identify what needs to be built; and, prioritize functionality.
Years of traditional plan-driven software development using conventional models have led to an assumption that conventional approaches are the only way to adhere to the best practices of project management. But the fact is that project management exists in agile methodologies as well. In fact, agile methodologies, if followed with discipline and rigor, are compliant with the best practices of project management, just as traditional approaches are. The only difference is command-and-control dictatorship Vs self-organizing teams.
Below table depicts the mixed bag of project management concepts like Scope Management, Risk Management, Quality Management, Integration Management presented as a comparison to the traditional approach to agile approach.S
|Scope Management||Risk Management|
|Scope DefinitionCreate WBSScope VerificationScope is decided in Release Planning & Sprint PlanningProduct backlog is regularly prioritized to reflect the Scope changesFeature acceptance at the end of each Sprint / Release||Risk IdentificationRisk ProbabilityRisk ImpactMitigation and Contingency PlanningMonitor & Control||Risks are identified and monitored regularly throughRelease PlanningSprint PlanningDaily StandupSprint RetrospectiveRisk monitoring can be any of the ways like recording results on whiteboards or flipcharts|
|Quality Management||Integration Management|
|Quality PlanningQuality AssuranceQuality ControlTest Driven DevelopmentTest Early & OftenCommitted QA resources from the beginningProject Plan developmentProject Plan executionDirect, Manage, Monitor, ControlChange ControlRelease and Sprint PlanningSprint ExecutionFacilitate, CollaborateConstant FeedbackScope is revisited at the end of each Sprint / Release||Test Driven DevelopmentTest Early & OftenCommitted QA resources from the beginning||Project Plan developmentProject Plan executionDirect, Manage, Monitor, ControlChange Control||Release and Sprint PlanningSprint ExecutionFacilitate, CollaborateConstant FeedbackScope is revisited at the end of each Sprint / Release|
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.