PMP® Study Notes

Notes for Agile


No CCB, No baseline

Fixed time and cost

Review with sponsor and allow change in next iteration

No project management plan but have product road map

Every round 2 - 4 weeks (1 - 4 weeks)

Minimum report

Agile methods are iterative and non-incremental

No overtime work

Agile no QA, use definition of done

Agile Leader - Enable team member to act

Sprints or iterations - short, repeatable phases, typically one to four weeks long. Each sprint should result in a draft, prototype, or workable version of the final deliverable

Sprint planning meeting - product owner, Scrum master, and Scrum team gather to decide what backlog items should be worked on during the next sprint. outputs are the sprint goal and the sprint backlog

Scrum - is a subset of Agile—a framework dedicated to developing, providing, and sustaining complex products, especially in the field of software development

Sprint review meeting - is the second last event of the Scrum sprint cycle where the Scrum master, product owner, development team, and stakeholders review the outcome and determine what can be closed off and what still needs work

Sprint retrospective - is a review of a past period of work. Emphasis on process and workflow. It’s used to evaluate both team and individual performance. Insights gained from a sprint retrospective informs the next sprint so that it can be even more successful than the last. Scrum helps an organization with continuous process improvement with its defined roles, artifacts, and ceremonies

Roadblocks - Lack of collaboration, Too few resources (additional hardware or software), poor prioritization, poor planning, lack of funding.

Product backlog - is a list that outlines the tasks that the development team needs to accomplish to create or improve a product

Sprint Backlog - is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).

Daily Standup - Organize by scrum master. A brief daily collaboration meeting in which the team reviews progress from the previous day and declares intentions for the current day, and highlights any obstacles encountered or even anticipated. Within 15 minutes in timebox. Product Owners should be at the Daily Scrum as they are a member of the team who has critical information to share

Product Roadmap - project artifact helps communication the goals, milestones, and potential deliverables, release, or other work outputs. The target audience is the sponsor and stakeholders

5 Scrum Values

1. Courage - Scrum team members have the courage to do the right thing and work on tough problems

2. Focus - Everyone focuses on the work of the Sprint and the goals of the Scrum Team. By working on only a few things at a time

3. Commitment - People personally commit to achieving the goals of the Scrum Team. E.g. Because we have great control over our own destiny, we are more committed to success

4. Respect - Scrum Team members respect each other to be capable, independent people. Working together and sharing successes and failures

5. Openness - The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work

12 Principles of Agile Manifesto

1. Satify the customer

2. Welcome change requirements

3. Deliver working software frequently

4. Business works with developers daily

5. Build projects around motivated individuals

6. Fact-to-Face conversation best

7. Working software matter

8. Constant pace

9. High quality code I faster

10. Maximize work not done

11. Self-organizing teams deliver quality

12. Feedback loops used to improve


Back