Abel Juarez
Outline
What inspired the new method? First commercial companies to use The 6 Keys to Managing New Process
Limitations
SCRUM in Software development
Basics Marketing Principles High Quality Low Cost Differentiation Characteristics Specialized Slow Rigid
process being used in 1986. The New New Product Development Game Companies studied (Projects) Fuji-Xerox (FX-3500-copier) Honda (City car) NEC (PC 8000-personal computer) Canon
(PC-10-personal copier, AE-1 single lens camera, Auto Boy (Sure
Multilearning
Subtle control Organizational transfer of learning
Built in Instability
Management initiates by giving a broad goal or general
strategic direction.
Team is given freedom Management also gives challenging requirements for the
been done
Cross-fertilization- Team members share knowledge with each
other
meet deadlines
At some point, the individual and the whole become
inseparable.
Pulse of the team is fastest in the begining and slows
Multilearning
Multilevel learning Multifunctional learning
Individual
Example: 3M, encourages
Experts encouraged to
Group
Example: Honda team members
sent to Europe
Subtle Control
Management still needs to check on team 7 ways for Subtle control
1. 2.
3.
4. 5. 6.
7.
Selecting right people for the project team Create open work environment Encourage members to get customer feedback Establish evaluation and reward systems Managing rhythm throughout Anticipate and tolerate mistakes Encourage suppliers to be self-organized
Transfer Learning
Team members and company use knowledge from project
Limitations
Requires great commitment from company and team
members.
Overtime
development is mastermined by a genius who makes the invention and hands down a well-defined set of specifications for people below to follow
Why?
Gantt charts didnt work Software was never finished when scheduled
Roles
SCRUM Master Keeps distractions away from team, makes sure goal are being met Product Owner Represents stakeholders(customers) and business, makes sure team delivers value
Development Team Project team, in charge of producing increments at the end of sprints
Terminology
Product backlog A prioritized list of high-level requirements. Sprint backlog A prioritized list of tasks to be completed during the sprint. Increment Sum of all the Product Backlog Items completed during a sprint and all previous sprints Sprint burn down chart Daily progress for a Sprint over the sprints length.
Sprints
Meetings
Sprint planning meeting Beginning of each sprint. Decide what is to be done during sprint Prepare Product Backlog Daily Scrum Short daily meeting during the sprint, where the team talks about how things are going
What did you do yesterday? What will you do today?
Meetings
Sprint review meeting Review sprint Present demo to stakeholders Sprint retrospective Review sprint process
What went well?
What can be done better next time?
Summary
SCRUM Method Team oriented Freedom leads to creativity Allows flexibility Knowledge is shared