Agile Project Management

Agile Project Management lets you produce minor deliveries i.e shippable functionality in an efficient and competent way in every iteration. It’s an ideal choice for teams who are working in product development, software design, corporate analys is and related domains.

Originally published at Hubpages

Agile, Lean, JIT is the terms which are IN nowadays for so many reasons, one of the most important is to keep the development/production cost low while keeping the focus on the Stakeholder needs which is ever changing because of the dynamic business environment.

The objective of Adaptive management is to continuously improve systematically. The stakeholders play a bigger role here then they do in Predictive environment.

Two Important Principles are;

  1. Iterative decision-making or making choices based on learning from the outcomes of decisions previously taken.
  2. Strategic flexibility or avoidance of irreversible decisions Some Important

Definitions one should know

  • Sprint: Iteration of delivery
  • Sprint Planning: Plan what needs to be delivered in the Sprint
  • Daily Standup: the daily gathering of all team members, answering what is done, what’s in progress and what are the problems
  • Product Owner A business Representative who is part of the team and attends daily sessions and do a business demo/sprint review at the end of the Sprint
  • Retrospective: At the end of the sprint, the team sits and relax and think over what went well, where they faced challenges, what they could improve and select what needs to be improved in the next sprint.
  • Product Backlog: A pool of user stories owned, managed and prioritized by Product Owner.
  • Release Planning: What would be released in which sprint
  • Timebox: Every action in an agile environment is time-boxed. 15 Minutes Daily Standups, 2 hours Retrospective, 2 hours demo, 4 hours Sprint Planning.
  • Velocity: no of user stories that can be delivered in any sprint. this is achieved over the period of time with the release of user stories in different Sprints
  • Burn down Chart: Tells you how many user stories are delivered. Its unique shape doesn’t allow anyone to cross the Sprint.

This requires a collaborative working environment so that teams can deliver effectively while welcoming a change. Every delivery edges towards a Product Skelton but based on the feedback received in Sprint Review after every Sprint.


Agile Project Management
Exhibit 1. The Original Scrum Framework Agile project management with Scrum CONFERENCE PAPER Agile Practices, Methodology


[pt_view id=”c356c37lza”]

One thought to “Agile Project Management – PMP/CAPM”

Leave a Reply

%d bloggers like this: