Agile 敏捷开发与Scrum流程

Sprint Planning
● Team selects items from the product backlog they
can commit to completing
● Sprint backlog is created
- Tasks are identified and each is estimated (1-16 hours)
Sprint backlog
Team
Sprint(Time box)
Burndown Chart
Scrum Process
Roles
Product Owner

Is (or is the representative of) the Customer
Defines and maintains the Product Backlog Prioritizes the Product Backlog Empowered to make decisions for all customers and users Presents and explains Product Backlog to team Scrum Team
the project
● Ideally expressed such that each item has value
to the users or customers of the product
● Prioritized by the product owner ● Reprioritized at the start of each sprint
Scrum & Agile
● Scrum & Agile Basics ● Scrum is a lightweight process framework for
agile development.
● A Scrum process is distinguished from other agile
processes by:
-- Specific concepts and practices, -- Three categories of Roles, Artifacts, and Time Boxes.
The Agile Manifesto
Individuals and interactions Working Software Customer Collaboration
over
Process and tools Comprehensive documentation Contract negotiation
over
over
Responding ting a plan
What makes Agile work?



Better collaboration with business More adapted to change/learning Communication Motivation Doing Less Collective ownership Time boxes




Inspect & adapt Focus on the real thing Three heads are better than one Collocation Information radiators Short feedback loops Team autonomy Accepted Responsibility
Daily Scrum Meeting
● Parameters
• Daily • 15-minutes • Stand-up
Everyone answers 3 questions
1 2 3 What did you do yesterday? What will you do today? Is anything in your way?

Continuous Improvement Absorb the Requirement change Rapidly-Responding. Benefit for Customer Values
My understanding is:
Development Model that meets above essentials can be regarded as Agile.
Sprint backlog
Tasks
Code the user interface
Mon
8
Tues
4
Wed
8
Thur
Fri
Code the middle tier
16
12
10
4
Test the middle tier
Write online help
8
12
16
16
11
8
Write the foo class
ScrumMaster

Guides the Agile Execution
Responsible for the process Responsible for maximizing team productivity Sets up and conducts meetings Representative to management and team Characteristics of a border collie or sheepdog
Add error logging
8
8
8
8
8
4
8
Burndown Chart
Displays the remaining effort for a given period of time.
Burndown chart should consist of:
X axis to display working days Y axis to display remaining effort Ideal effort as a guideline Real progress of effort
- Collaboratively, not done alone by the ScrumMaster
● High-level design is considered
e.g.,
As a vacation planner, I want to see photos of the hotels.
Code the middle tier (8 hours) Code the user interface (4) Write test fixtures (4) Code the foo class (6) Update performance tests (4)
Certain Knowledge
Action
Sequential vs. Overlapping Development
Requirements
Design
Code
Test
Rather than doing all of one thing at a time... …Scrum teams do a little of everything all the time
-- If using Fibonacci series, usually consider not using 1 and 2. -- Find a baseline story
Sprint Review
● Presents what is accomplished ● Takes the form of a demo features ● Informal
• •
2-hour prep time rule No slides
● Whole team participates
Store Point
● Story point is an arbitrary measure ● 1,2,4,8,16 ● XS, S, M, L, XL.
● Fibonacci series - 1,2,3,5,13,40,100
-- Abstract - NOT directly co-relate to actual hours.
Agile & Scrum
Loic Lee
Concept of Agile
● What do you think Agile is? ● Agile Philosophy
---- Result is the most important thing, all procedures or approaches are used for serving it . If the procedure leads to the unexpected results, then we should improve it.
● Invite the world
Sprint Retrospective
● Periodically take a look at what is working and
what is not
● Typically around 30 minutes
● Done after every sprint
● Whole team participates
• ScrumMaster
• Product owner • Team
• Possibly customers and others
Product Backlog
● The requirements – A list off all desired work on
Overview
Scrum Framework
Roles
Product Owner
Ceremonies
Sprint planning
Sprint review
Artifacts
Product Backlog
ScrumMaster
Sprint retrospective Daily scrum meeting

Performs the work directed by the Customer
Self-organizing Typically 5-9 performers (Cross-functional) Business and technical skills to build an increment of functionality Responsible for estimating and committing to work Full autonomy and authority during a Sprint
The Big Paradigm Shift
We’re used to Time Lines Project Managers Fixed Budgets Predictable, all at once deliverables Multiple matrixed units in multiple locations make up team Communication by Document Customer is removed Agile Wants We’re done when it’s done. Disciplined self managing teams. Assumed change means no fixed cost. Incremental deliverables driven by value and constant learning. Co-location – one team. Information Radiators. Customer is part of team.
● Not for problem solving
• Whole world is invited
• Only team members, ScrumMaster and product owner can talk
•
● Helps avoid other unnecessary
meetings
These are not status for the ScrumMaster. They are commitments in front of peers.