acp project management institute agile certified practitioner exam study guide B u s i n e s s F i n a n c e

acp project management institute agile certified practitioner exam study guide B u s i n e s s F i n a n c e

There are two person’s opinion about the discussion board questions. i have to reply them separately.

just give your opinion based on their post.


reply for person 1 (damodar) post……

reply for person 2 (Michael) post….

Topic: Adopting planning

Person 1 post: damodar

This week’s video discussed agile planning. The presenter explained how the agile planning works, how to create an agile plan, and how to respond to the changes. In the current competitive business world, organizations should have the capacity to make changes or respond to changes. The presenter’s traditional project management methodologies, referred to as static planning, emphasize following the project plan with minimal changes. In static planning, the project is completed on time and within the budget, with the predefined features and functions. Although this approach seems to be more comfortable, it does not allow flexibility to make changes required due to uncertainty involved in the project life cycle. As the presenter mentioned, the organizations should have the ability to plan the projects so that the changing teams, reduced schedules, or changing requirements do not impact the projects.

Unlike static planning, the presenter has introduced agile planning, also called adaptive planning. The agile planning focuses on delivering great value to the customers and making promises that can be delivered. Agile planning is highly visible, open, and honest and provides the opportunity to make changes when necessary. As the presenter mentioned, agile planning focuses on the idea that the agile teams should promise only what they can accomplish based on the team velocity. The speed with which a team can turn the user stories into a completed product determines the team velocity. Team velocity is critical in agile planning. It helps determine the team’s productivity and set the expectation around the finished products’ delivery dates. The team velocity could vary initially, but after a few iterations, the agile team will develop the team chemistry, and it will be much easier to determine the team velocity. The customers decide what they want to see in their final product, and it is captured in the master story list. So, once the team velocity is determined, the iterations and time required to complete the master story list are determined.

As the team velocity is hard to determine initially, the presenter mentioned that the project plan should not be the hard commitment. If taken as hard commitments, the initial plans could bring chaos in the projects because the project may take a longer time to finish and even cost more. The rigid project plan could result in unwanted or unnecessary projects or product results. The presenter thus presented the idea that agile planning provides the flexibility on the project scope or delivery date to achieve the project goals and add value and quality to the project or product results.

The presenter has also discussed how agile planning can be done, which can be executed and updated as needed. At first, all the user stories are grouped to create a master story list. Based on user stories, the agile team sizes them up for the estimation. The customers ask for what they want first, but the agile team should facilitate the customers on how to prioritize the user stories. The essential part of agile planning as mentioned earlier, is estimating the team velocity. Once the team velocity is determined, the delivery dates should be discussed with the customers. The customers can choose between delivering by date or deliver by feature set.

Unlike the traditional static project planning, adaptive planning prepares the agile team to respond to inevitable changes. Adaptive planning focuses on adapting to the changing nature of the business world. Adaptive planning focuses on reviewing and revising the project plan as the project progress to accommodate the various changes required to achieve the project goals and add value and quality to the project or product results. Also, adaptive planning considers the importance of team velocity in measuring the team’s productivity to delivering the quality product on expected dates. The adaptive planning thus helps in developing products that can sustain in the market.

This week’s video helps me better understand one of the agile manifestos ‘Responding to change over following the plan’. As we know that the ability to both create and respond to change to profit in a turbulent business environment is very critical to the organizations. The presenter has described how adaptive planning provides the ability to make changes when necessary, which delivers better quality and value. As the presenter mentioned, the project team should be in the position to promise only what they can accomplish. Since the customers are involved throughout the agile projects, the agile team should consider customers’ feedback and availability to determine the team velocity. The agile team should have a clear understanding of done to deliver only the finished products. The most important point mentioned by the presenter is that the initial project plan should not be the hard commitment as the need for the modification to the project policies or procedures, project or product scope, project cost or budget, project schedule, or quality of the project or product results may require as the project progress.

Understanding the importance of agile planning is essential in a competitive business environment. As we have seen that the companies like Blockbuster that failed to make the change and stayed with its traditional business model ended up filing for bankruptcy while Netflix emerged as a giant online video service provider by exploring and innovating new ideas to establish the brand. The knowledge of adaptive planning would equip me with the idea that the project team should be flexible in reviewing and revising the project plan based on the stakeholders’ feedback as the project progresses. As a team member, I should develop the capacity to determine how much work can be accomplished to choose the delivery dates.


Rasmusson, J. (2013, June 19). Agile Planning.

Here is my post about adoptive planning: sapna999

Adaptive Planning

The key content from the assignment is understanding the planning process of delivering software. The issues that one needs to understand change and adapting to change. According to Rasmusson (2016), in the process of planning to deliver software, disruptions can occur, for instance, a change in the team, customer preferences, or delivery dates. These changes impact the planning process making it hard to deliver the software as pre-agreed. However, through agile/adaptive planning, Rasmusson (2016) notes that teams can create better schedules. The author defines agile planning as the technique where developers determine the time it will take them to deliver programs to the consumers; this is done by estimating the time it will take to accomplish each user story. This technique enables better planning because it does not just estimate the when production-ready software will be delivered but accounts to short-term efforts needed to deliver short-terms goals (referred to as iterations). , Rasmusson (2016) further recommends adaptive planning due to its flexibility, that is, one can choose whether to flex on the delivery time or the delivery scope; this means the team is not working on a fixed production plan which reduces pressure.

Apart from learning about adaptive planning, other key takeaways from the video are; first, one should not create fixed commitments in the initial stages of the project. Rasmusson (2016) notes that when starting, the team does not know its capacity; hence the delivery times keep on fluctuating. However, as the team progresses, it begins to know their capacity hence get better estimates of what they can deliver and when. The second key takeaway is that one should give their inputs on the urgency of the different deliverables. Rasmusson (2016) notes that the customers have the right to dictate what they want to be delivered; however, the programmer should also give their input on what they consider important. The third takeaway is that a done project is a done project. The narrator notes that the team should understand that when they say they are done; it should imply that everything has been completed: from coding to analysis. The last takeaway is that setting the date comes after considering all other factors. The narrator recommends that one should start with creating the master story list, then sizing the stories (by the effort needed), followed by giving priority (where the most critical stories are given higher priority) and lastly estimating the speed with which the team can finish the stories. By setting the delivery date last, one is more certain that they can meet the deadline.

The concept of adaptive planning will have great impacts on my future projects. It has shown me that planning a project is a process; one should not just set a date for delivering the project. In the future, before I start working on a project, I will first identify what is needed and assess it with my ability (or team’s capacity) to determine the time I will take to deliver then setting the delivery time. Through these steps, the project will be more flexible hence better to handle changes, for instance, if a customer changes their deliverable, rather than restating the whole project, I will only need to change the affected story. Therefore, adaptive planning is an essential technique in projects.


Rasmusson, J. (2016). Agile Planning: Dealing with reality. Accessed from: