Online Mind Mapping and Brainstorming

Create your own awesome maps

Online Mind Mapping and Brainstorming

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account? Log In

Agile Project Management With Scrum - Book Notes by Mind Map: Agile Project Management With
Scrum - Book Notes
4.8 stars - 4 reviews range from 0 to 5

Agile Project Management With Scrum - Book Notes

Empirical Process






Scrum Master

Teaches scrum to other members

Ensures the scrum process is followed and successful

Product Owner (PO)

Represents the interests of the stakeholders

Provides initial overall requirements, Product Backlog, Always changing, Initial estimates and priorities, Dynamic, always updating and changing, Large Printout in team area so everyone knows the goals and progress

Focused on Return on Investment (ROI)


Responsible for developing functionality

Self managing and self organizing

Responsible for success of each iterration

All role members have authority in each area

Committed to the project, Those not committed cannot intefere

Pigs and Chickens analogy

Pig and Chicken discuss opening a restaraunt, Only going to serve Ham and Eggs, Thus the pig is the only real committed role, Chicken desires the project to be successful, but has no real work to do and isn't on the hook for its success


30 Day Iteration

Sprint Planning Meeting

Time Boxed: 8 Hours Maximum

Product Owner and Team meet to discuss what will be done for the next sprint, Chosen based off priority of the Product Backlog, Team should practice communication skills with the Product Owner to speak about business not technically

2 Parts, First 4 hours, Work with PO to update/ add to and prioritize Product Backlog, Discussion includes content, purpose, meaning, and intentions of the Product Backlog., Second 4 hours, Team creates a plan to work off agreed upon tasks, Agreed upon tasks are called Sprint Backlog, Tasks are created and assigned, May not be complete/comprehensive but enough to get the team started and on track to complete all tasks, Estimate hours on task, Estimations need to include design, unit testing, refactoring, peer review, Should include formal 'testing' tasks until the team understands 'done' means everything from desing->code->refactor->fully tested, Marks the beginning of the 30 day sprint

Daily Scrum

Every Day, 15 min

Answer Three Questions, What have you done since the last scrum, What you plan on doing until the next scrum, What roadblocks you have for this sprint or the project

Synch up team and schedule any meetings needed to forward its progress, find out what is behind and if all tasks are going to be finished

Mention detail, Do NOT say 'bug fixes', state which bug, in what code, allow team members to offer help or insight

Find out who needs help, schedule help asap

Sprint Review

Time Boxed: 4 Hours

Team presents what was developed to the Product Owner, Other stakeholders can attend

Sprint Retrospective Meeting

Time Boxed: 3 hours

ScrumMaster encourages the Team to revise, within the Scrum process framework and practices,

Each team member states what worked in the sprint and what needs to be improved

Complex Projects

Scrum of Scrums

One member from each team meets for a separate daily scrum

Part time team members

A team member from one team will take part in other team's daily scrums to coordinate dependencies. This makes them a part time team member.

Sprint Review Meetings can be mixed as a demo day

Should replace formal documentation and reporting on the sprint

Scaling Scrum

Adding Number of Teams, Sprints to setup archiecture required before scaling teams, New teams are seeded with a member of original team

Non functional scaling requirements need to be added to product backlog, Staging, Decompose business architecture to support clean-interface multi- team development, Decompose system architecture to support clean-interface multi- team development., If necessary, define and implement a development environment to support multi-team collocated or distributed environments.


Apendix A has great high level rules