Agile

• Scrum Reference Card - http://scrumreferencecard.com/scrum-reference-card/
• Scrum Guide - https://www.scrum.org/Portals/0/Documents/Scrum%20Guides/2013/Scrum-Guide.pdf
• Agile Methodology - http://agilemethodology.org/
• Scrum Training Series - http://scrumtrainingseries.com/Intro_to_Scrum/Intro_to_Scrum.htm

Questions

References

• Specifies how to achieve the PBI’s what
• Requires one day or less of work
• Remaining effort is re-estimated daily, typically in hours
• During Sprint Execution, a point person may volunteer to be primarily responsible for a task
• Owned by the entire team; collaboration is expected

• consists of committed PBIs negotiated between the team and the Product Owner during the Sprint Planning Meeting
• scope commitment is fixed during Sprint Execution
• initial tasks are identified by the team during Sprint Planning Meeting
• team will discover additional tasks needed to meet the fixed scope commitment during Sprint execution
• visible to the team
• referenced during the Daily Scrum Meeting

Sprint Task

Sprint Backlog

Sprint Tasks

Sprint Backlog

Scrum Artifacts

Product Backlog

• scrum team (including product owner) attends
• time boxed to 3 hours
• inspect how the last sprint went
• identify major items that went well and potential improvements
• create a plan for implementing improvements

• Force-ranked list of desired functionality
• Visible to all stakeholders
• Any stakeholder (including the Team) can add items
• Constantly re-prioritized by the Product Owner
• Items at top are more granular than items at bottom

Agilility

Product Backlog

Sprint Retrospective Meeting

• improve communications, eliminate other meetings, identify impediments to development

Agile Methodology

• What did I do yesterday that helped the Development Team meet the Sprint Goal?
• What will I do today to help the Development Team meet the Sprint Goal?
• Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

• alternatives to traditional project management
• emphasizing adaptability
• help businesses respond to unpredictability

Rational Unified Process

• development team attends
• talks about the last 24 hours, and the next

Lean

eXtreme Programming

Sprint RetrospectiveMeeting

Crystal Clear

Scrum

Kanban

Feature Driven Development

• cross-functional team (includes all skills required)
• self-organizing / managing
• negotiates commitments with product owner
• most successful when located in one room (particularly for first sprints)
• most successful with long-term membership
• Small team size, between 4 and 9

Daily Scrum

Sprint Review Meeting

Development Team

Development in an Waterfall Team

Daily Scrum

Scrum Meetings

User Interface

Connectivity Layer

Sprint Planning Meeting

• whole project length
• hard to judge completeness
• hard to meet changing requirements

• product owner, team and stakeholders attend
• time-boxed to 4 hours
• explanation of what's been done and demonstrates
• discussion of the product backlog, with revisions
• discussion of what to do next

Business Logic

Persistence

Development

Team

Scrum

Master

Product

Owner

Business Logic

• iteration is 1 month
• regular checks for completeness
• regular opportunities for adapting to changing requirements

Connectivity Layer

Sprint Review Meeting

User Interface

Development in an Agile Team

Scrum Roles

• product owner and team attend
• time-boxed to 8 hours
• negotiate product backlog items to commit to the sprint
• team decides what to commit to, not product owner
• a sprint goal is created, "the selected Product Backlog items deliver one coherent function, which can be the Sprint Goal"
• once the goal is set, team determines how to achieve the goal (system design, decomposed into tasks)

Sprint Planning Meeting

• facilitates Scrum process
• shields the team from external interference
• enforces timeboxes
• keeps Scrum artifacts visible
• promotes improved engineering practices
• no management authority over the team

• single person
• responsible for product vision
• prioritizes backlog
• considers stakeholder interests
• accepts or rejects each product increment
• decides whether to ship, continue development

Scrum Master

Product Owner