Agile Project Management
What is Agile Management? According to “Information Technology Project Management” it is defined as “being able to move quickly and easily, but some people fell that project management, as they have seen it used, does not allow people to work quickly or easily.” Agile can be used for software development or in any environment in which the requirements are unknown or can quickly change. The agile approach during the triple constraint phase sets the time, and cost goals but leaves scope goals flexible so the project sponsors or product owners can prioritize and reprioritize the work that needs to be completed. (infotechprojmngt) Using an agile development model, you still do the same type of work as you would use a traditional waterfall model: You create requirements and designs, you develop your product, and you integrate your product with other products as necessary. You test the product, fix any problems, and deploy it for use. However, instead of tackling all the steps for all of your product features at once, you break the project into iterations (smaller segments of the overall project), called sprints. While there are several process differences between traditional project management and agile, the most significant shift is from hierarchal-based responsibility and task assignment in favor of the “self-organized” team-based approach. Traditionally, the onus for project success has resided with the project manager by creating, communicating and executing on a completed and linear project plan. In Agile, the whole team is responsible for success. (infotechpromgmt)
In the phases of a traditional waterfall development arc, you move to the next phase only when the previous one is complete. So that stages of a project resemble a waterfall: 1. Requirements 2. Design 3. Development 4. Integration 5. Testing 6.