Professional Documents
Culture Documents
Goals
Introduce the Scrum Framework Establish a common language Understand roles & responsibilities Learn how to plan a project Learn practical techniques for implementation Understand what life is like on a project using Scrum Learn where to look for additional information
Agile Infusion, LLC 2007-2009
Exercise
Learning Objectives
Exercise
Self-Organize
Introduce yourself to your team Share your personal objective(s) for the course As a group, identify some common goals and
issues of interest
Develop 5 questions about Scrum that your group
Agile Terminology
Agile Development
Time-boxed Iterative Incremental Feature-based Business/User Value-driven Agile values and practices that encourage rapid and flexible response to change
Scrum One of the agile development methods Agile project management framework Others
XP, Lean, DSDM, Crystal, etc.
Agile Infusion, LLC 2007-2009
Contract negotiation
Following a plan
Agile Manifesto 2001, www.agilealliance.org
Agile Infusion, LLC 2007-2009
DONE
Scrum Workflow
Key Practices Self-directed; self-organizing teams (preferably co-located) Iterative Adaptive planning Stakeholder/Customer Involvement 30-calendar day iterations 15 minute daily stand-up meeting Team measures progress daily Each iteration delivers tested, fully-functional software for demonstration Always 30-days from potential production release Sprint Retrospective Process Create a rhythm and flow
Obstacles Removed
Release Backlog
Planning / Retrospective
Product Roadmap Business Goals
Product Owner
and content Is responsible for the profitability/value of the product (ROI) Prioritizes features according to market and/or user value Can change features and priority every 30 days Accepts or rejects work results
Ensures that the team is fully functional and productive Enables close cooperation across all roles and functions
ScrumMaster
and removes barriers Shields the team from external interferences Ensures that the process is followed. Invites to daily scrum, iteration review and planning meetings
Cross-functional, seven plus/minus two members Selects the iteration goal and specifies work results Has the right to do everything within the boundaries of
Team
the project guidelines to reach the iteration goal Organizes itself and its work Demos work results to the end-user and stakeholders
Agile Infusion, LLC 2007-2009
Scaling Scrum
Large Projects Many Teams
Product Backlog
- Functional requirements - Non-functional requirements
Complex Backlogs
Agile Infusion, LLC 2007-2009
Backlog Items
Goal: Priority:
Goal:
May also include: Major Assumptions Conditions of Satisfaction Key Points of Conversation Anything else you need Goal: Goal: Goal:
Priority:
Priority: Priority: Priority:
Backlog Lifecycle
Product/Release Backlog
Deliverable Product
Priority
Feedback
100% Tested
Demonstrate ability to support features Every Sprint must deliver at least some piece of business functionality
To prove that architecture or infrastructure works To prove to customer that work they value is taking place
Information Gathering
Exercise
Develop a backlog for a new website for our hobby
Establish 3-4 Prioritized Business Goals Write 10 User Stories for the Site Connect User Stories to Business Goal Assign points based on estimated size
1, 2, 3, 5, 8, 13, 20, 40, 100
Assign business value of High, Medium, Low Prioritize the list (Rank Order 1-10)
Agile Infusion, LLC 2007-2009
Family Scrum
Exercise
Using our hobby website backlog
Develop a release plan Use an estimated velocity of 12 points per sprint What does your plan look like? How did you maximize value? What is the outcome-based goal of the 1st sprint?
Agile Infusion, LLC 2007-2009
Scrum Team How are we going to meet Sprint goals? Determine team capacity Break sprint backlog into tasks Estimates no greater than 16hrs Team plans how it will work together to deliver Review of Done Identification of Obstacles/Risks Identification of Dependencies Identification of conditions of satisfaction (tests, inspection..) Review Sprint Backlog with PO
Velocity
What is the rate at which we convert backlog items to done increments Depends on History, Lessons Learned, Risks, Capacity, Skills, Environment, Tools
Exercise
You are a team working on a project
You are all 100% allocated to the project Your productive hours/day is 5 Use your own schedules for vacation, meetings, etc.
What is your teams capacity for the 4-week sprint that starts today?
Tasks
(hours)
Work Remaining
Update work remaining on tasks for burndown Not a problem-solving or design session
Scrum Master reports on obstacles Chickens invited to listen and observe Remote?? Try a virtual meeting like this
Agile Infusion, LLC 2006-2009
Quality
Continuous Integration & Testing
Strive to get continuous builds Full testing of each increment at every level possible Automate, Automate, Automate!!
Defect Management
Maintain high quality through each sprint Do not build the bug mountain Log all issues from start of project that do not get closed by end-of-day
Traceability
From Vision to Goals to Features to Backlog to Tasks
Maintainability
Quality designs, Simplicity, Fully automated Unit to Systems tests
Usability
Sprint by Sprint feedback and adaptation to users needs
Agile Infusion, LLC 2007-2009
Scrum Environments
Workspaces
Team Rooms
Level 1
Sticky Notes; 3x5 cards, whiteboards, easel sheets
Level 2
Excel Spreadsheets with Scrum Macros
Level 3
Free; Low Cost Solutions Many of these
Level 4
For Complex Project/Programs VersionOne, Rally Others
Exercise
THANK YOU!