PMI-ACP Certification: Adopting an Agile Approach

The Agile Manifesto

Organizations across the world are using agile project management to get superior results. But this doesn't mean that the move from traditional to agile project management will be easy. One of the main challenges is overcoming the various myths and misconceptions about what an agile approach involves.

The Science of Better Learning

The approach you adopt doesn't have to be purely agile or purely traditional. Instead of viewing different project management methodologies as black and white, you should view them as points along a continuum, with many shades of gray.

Contrasting Historical Project Management with Agile Project Management

Agile development requires just enough documentation. Creating unnecessary documentation is considered a waste of valuable development time.

Identifying Useful Documentation

Although agile methodologies were first geared towards software development projects, they're not just development methodologies. Instead they're project management methodologies.

Planning in Agile looks very different. In agile development, there's no work breakdown structure or time-phased and resource-assigned task list. Instead Agile uses just-in-time planning.

Various misconceptions about agile methodologies may prevent or hinder their adoption. Learn agile project management to apply it effectively.

Using an agile methodology may have a tremendous impact on a project. It can shorten development cycles, improve quality and efficiency, lower costs, and result in better customer satisfaction.

Alignment of the agile transition team

The structure of an organization is one of the key factors that determines how easily it will be able to transition into using an agile methodology.

Agile Pain Points and Troubleshooting Possibilities

The nature of the existing project management processes in an organization will help determine how easily a team can adapt to using an agile methodology. Generally, the more flexible and informal these processes are, the easier a team will find the transition.

The nature of your organization's industry is an external factor that may affect the suitability of an agile approach. Industries that are relatively stable tend to focus on updating or improving products that have already been tried and tested. They have a steady customer base and know their product and competition.

Which characteristics indicate that agile practices may be appropriate for this company and project?

Application of Agile in PMBOK Knowledge Areas

It's not always appropriate to adopt a fully agile approach to project management. Organizations might not be ready to commit to the level of change and training that this requires.

Different agile methodologies use different techniques for defining requirements, and project teams may customize these to suit their needs.

Another general agile practice you can adopt is iterative development with incremental delivery. Instead of completing all project work and then delivering the result to the customer for review, you focus on completing regular, short bursts of work and delivering the results to the customer at the end of each cycle.

A final agile practice that can benefit most organizations and projects is frequent, open communication among project team members, and between the team and the project customer.

Agile methodologies don't generally prescribe exactly how you should manage a project. Instead they define principles that you can interpret and implement in your own way. By introducing these principles gradually into your workplace, you can transform the way your project teams operate.

Although lean principles can form the basis of an agile mindset and are generally easy to implement, they're not the only core principles used in an agile approach. Once you've introduced these principles and your team is familiar with them, you can begin introducing other agile principles.

An important step in the process of adopting agile practices is to obtain buy-in from stakeholders in your organization. Switching from a traditional approach to project management to an agile one involves making significant changes – and change can be difficult for people to accept.

When communicating the need for change to stakeholders, you should focus on explaining the weaknesses of the traditional – or waterfall – model your organization currently uses.

The next step in convincing others of the need to move from a traditional approach to a more agile one is to explain the potential benefits for the organization. When doing this, you can focus on three main benefits – reduced risk, improved control, and improved communications.

Statistics that prove the effectiveness of Agile practices to review some statistics you can use when explaining the benefits of adopting an agile approach.

When you tell stakeholders about agile project management, you should be open about the risks or pitfalls involved. This gives the message that you're not trying to convince them to use agile practices, but that the organization's interests are a priority and that you want them to make an informed decision.

A project covering the main steps in adopting agile project management.

Course wrap-up, learning objectives review and next steps.

This course covers the key exam concepts of Kanban, work in progress or WIP, lead time, cycle time, and Little's Law. You'll also learn about Agile Team Spaces, sharing the product vision, and identifying and reducing defects. 

In Lean project management waste, or the Japanese term Muda, is defined as any activity or process that doesn't add value to a product but does add cost. Lean's original Seven Forms of Waste include transportation, inventory, motion, waiting, overprocessing, overproduction, and defects. The new eighth form of waste is skills or non-utilized talent. 

In a Pull-based system, the customer demand creates what is called pull. Production or development relies on pull rather than on complicated market forecast to determine how many products to deliver.

A Kanban board is a tool that agile teams often use to visualize workflow through a system. While Kanban principles are often used in IT and software development, they can be helpful in any industry.

In lean project management, one of the key concepts is process improvement. Lead time and cycle time are two important metrics that help determine how lean a process is. In other words, how much of the time dedicated to creating a product is value added. 

Lean manufacturing is a management philosophy that focuses on reducing waste and implementing a flow-based production line rather than a batch and queue method. It's aimed at reducing costs and improving overall customer value. 

In order to maintain a stable process with minimal chaos organizations should attempt to minimize work in progress or WIP in their processes. One way to do this is by setting WIP limits. WIP limits help to reduce bottlenecks, improve the rate of throughput, and control the workload levels of project team members. 

Stakeholder engagement is a fundamental part of project management. It's important to be able to express the product vision to stakeholders in order to gain support in common understanding about the product requirements. The product owner often collaborates with other key stakeholders to develop a product vision. 

With today's modern technology there are a variety of tools to bring teams together virtually. 

Agile teams achieve efficiency by leveraging many of the tools from Lean Management, but also by valuing individuals and interactions. 

In this exercise, you'll demonstrate that you can identify characteristics of waste
recognize the relationship between PCE variables identify characteristics of Agile environments 

This course covers the key exam concepts of Kanban, work in progress or WIP, lead time, cycle time, and Little's Law. You'll also learn about Agile Team Spaces, sharing the product vision, and identifying and reducing defects.

You think knowing stuff changes the game? You think sitting in a library, stacking up facts like you’re building a Jenga tower, is gonna make you a winner? Man, that’s cute. But life ain't a trivia night. Information alone? It’s worthless. It’s like having a Lamborghini in your garage but you never learned how to drive. You just sit in it, making engine noises. Vroom vroom. People walk by, they see the car, but they also see you ain't going nowhere. You got all this knowledge, all these textbooks, but when life throws a punch, you’re still looking up the definition of "duck." It’s what you *do* with that information that actually matters. Don't be the person with the shiny car and no keys.