Agile project management can transform your career
Agile Certified Practitioner (ACP(r),) certification from Project Management Institute is for agile project managers. Agile can be used to describe a variety of light-weight software development methods. Agile was developed in response to the serious issues in the heavy-weight waterfall software development model. Agile methods emphasize iterative and incremental software developments, customer collaboration, value driven design, and flexibility to change. Based on its project database from 2002 to 2010, the 2011 CHAOS Manifesto shows that agile project success rates are three times higher than water-fall! Customers also get faster returns on their investment and early deliveries. Customers are choosing agile more than ever. Project management community wanted to know agile and agile project management. ACP from PMI is the perfect solution. PMI faced the challenge of framing its contents, as you can see. It was faced with multiple agile methods. It has a team of agile veterans and this is evident in the well-formed ACP contents. ACP talks about the Agile principles and manifesto, which form the foundation for all agile methods.
You can read about popular agile methods such as scrum and Extreme Programming (XP), as well as other agile methods such as FDD, DSDM Crystal, openUP Kanban, Kanban, Lean, and Crystal.
Agile planning is multilevel, progressive and adaptive. It can plan product-level planning, release planning, and daily planning. Agile emphasizes the fixed time box concept in its meetings and iterations. e.g. Iterations must be completed within the time-box interval. This may compromise scope. Agile uses relative estimation which is faster, more accurate and easier than traditional methods.
Agile uses ‘just barely adequate’ requirements and design documents. Agile requirements are a single liner (known to customer as user stories). Before implementation, the team talks with customers to understand the requirements. Agile believes that living code is a better design document than large, often outdated, design documents. Agile believes in an evolving and adoptive design and does frequent revisions.
The customer defines the value of each user story from both a business and end user perspective. This information is used to order the stories. This allows customer to have the flexibility to end the project at any time and ensures that the most valuable requirements are met first.
Agile emphasizes good software engineering practices such as continuous integration, test automation (TDD), and pair programming
Agile teams are cross-functional, self-managing and empowered. The team works directly with customers from requirements collection, estimation, planning and execution, continuous improvement, control, monitoring & controlling, continuous improvement, change management demonstration and delivery. Agile emphasizes collective code ownership and team accountability for delivery. The Agile team uses simple tools such as Kanban board, burn-up/down charts and signal lights. They also use information radiator to manage their projects. These tools are easy to understand and maintain. The role of the project manager would change to that of a coach, facilitator, clearing impediments, and supporting the team.
Agile values colocation, face-to-face communication, less documentation and continuous customer collaboration. Agile also adopts a distributed team with the help modern communication tools
To be a future manager, join the ACP community.