Roles: Scrum Master & Project Manager
Project Manager:
Validate project alignment to vision Perform Release Planning
Deliver successful project Track project performance
Identify areas impacting quality
Escalate Risks and Issues beyond project Manage Companion and Dependent
project interactions, impacts, and participation
Manage and communicate project status
and metrics while balancing time, cost, and scope
Manage delivery against major milestone
and objectives
Manage project staffing and invoicing
Scrum Master:
Facilitate collaborative meetings Track team performance
Remove impediments (Risk, Issue)
Validate team alignment to Agile framework and scope
Drive accountability and
cooperation of team members Deliver working software
Define level of expected quality Drive planning milestones
Mentor team members
Focus on a single work stream and how it could impact others Request external group
Roles of the Core Team
Developer:
Creates working software Adheres to coding standards Practices Test Driven Design
Collaborates with BA and Testers
2
Business Analyst:
• Facilitate scope workshops
• Understands the business needs • Focuses on the business value • Creates artifacts
• Supports developers • Works with Testers
Tester:
Identifies User Stories that are “Done”
Creates test plans Performs testing
Updates quality metrics Manages defects
User Experience Designer:
Facilitates design workshops Defines usability
Conducts usability testing Usability Focus
Agile Team Skills
Problem Solver Visionary Product Knowledge Supportive Deals with Ambiguity Supportive Applies WIT Attitude Adaptable to Change Able to Multi-task Strong Leadership ForwardThinking CommunicatorEffective
Planning:
Product Vision & Roadmap
ID Task Name Start Finish Duration
Q1 13 Q2 13 Q3 13 Q4 13 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
1 Loyalty 03/04/2013 09/06/2013 27w
2 Guided Navigation 05/06/2013 02/28/2014 43w
4 Mobile Presentation 07/08/2013 11/22/2013 20w
3 Open API’s 01/07/2013 06/06/2014 74w
Q1 14 Q2 14 Q3 14 Jan Feb Mar Apr May Jun Jul Aug Sep
6 Product Vision:
•Validate and assess target market •Determine user needs
•Identify critical product attributes
•Assess existing products (internal and competitor) •High-level target timeline for launch
•Estimate ROI
Development:
Project Plan – Trade-offs
The total points identified within the “Trade-off Sliders” table
should equal 15 points in order to ensure balance.
Points included in the Trade-off Sliders matrix can be adjusted to
the focus or interests within a company, department, or project.
The project Trade-offs are used to review to project decisions
Balancing the Triple Constraints
8
Cost Time
Scope Product
Development:
Development:
Sample Release and Iteration Plan
Development:
Development:
Sample Iteration Plan
Agile Scope Management
Product Backlog identifies high level requirements
User Stories and User Story Narratives further define the
requirements
Proposal Project
Sample Governance Model
Proposal Project
Scope:
Sample Life of a User Story
Traceability of Project Scope
Agile Methodology Artifacts
Agile Project Type Decision Tree
Product Backlog
User Stories
Project Management Plan
Work Breakdown Structure
Agile Guiding Principles
18
Agile Project Type Decision Tree
What
– tool to determine if project
team is setup for success with
Agile methodology
Why
– provides guidance on what
projects fit into Agile methodology
Agile Project Type Decision Tree
Product Backlog
User Stories
Project Management Plan
Work Breakdown Structure
Agile Guiding Principles
Product Backlog
What – list of all requirements that will
be considered for the end product
Why – critical tool in Scope
Management
Who – BA is responsible to maintain
When – throughout the project
Agile Project Type Decision Tree
Product Backlog
User Stories
Project Management Plan
Work Breakdown Structure
Agile Guiding Principles
20
User Stories
What – S
ingle document used to
define the system requirements,
use cases, and functional design
for an iteration
Why – Provides for a one document
view of requirements from which developers can work
Who – BA is responsible to maintain
When – throughout the project
Agile Project Type Decision Tree
Product Backlog
User Stories
Project Management Plan
Work Breakdown Structure
Agile Guiding Principles
Project Management Plan
What – Outlines management
practices for all areas of project management
Why – Provides single view of how the
project is being managed using Agile methodology
Who – PM with input from team
When – Created in Iteration 0, updated
throughout the life of the project
Agile Project Type Decision Tree
Product Backlog
User Stories
Project Management Plan
Work Breakdown Structure
Agile Guiding Principles
22
Work Breakdown Structure
What – Agile schedule template
Why – Offers alignment of iterative
development for Agile projects to help manage the sprints, releases, and project budget based on resource allocation.
Who – PM with input from team
When – Created in Iteration 0, updated
throughout the life of the project
Agile Project Type Decision Tree
Product Backlog
User Stories
Project Management Plan
Work Breakdown Structure
Agile Guiding Principles
Agile Guiding Principles
What – Reference document which
provides standard process, artifacts, and tools for Agile methodology
Why – Improve Agile planning,
practices, and process alignment
Who – All project participants
When – New to Agile or as needed for
review
Agile Scope Prioritization
Benefits Investments
Needs
Agile Scope Estimation
26
Planning Poker:
Finite Scale for Story Points
0, ½, 1, 2, 3, 5, 8, 13, 20, 40,
100, ?
Large stories should be split
Not enough information to
estimate
Triangulate Story Point
Estimates
Compare stories with similar
Agile Metrics
Burn down Charts
Agile Demos
28
Demonstrate working
product functionality
Not a slide presentation
Gain alignment / direction
on product functionality
Input into Product Backlog
Agile Retrospectives
Valuable tool offering ability to
adapt learnings going forward
Safe environment to share
What worked well?
