scrum
DESCRIPTION
Overview of why SCRUM can add value to the development process.TRANSCRIPT
![Page 1: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/1.jpg)
SCRUM
Jeremy Thomas
Development Manager
Consumer Media
active.com
![Page 2: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/2.jpg)
SCRUM is a collaborative approach to building software. Testers, engineers, product developers
and even IT work together from start to finish.
![Page 3: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/3.jpg)
SCRUM acknowledges that chaos is present in most system
development projects. SCRUM maximizes the amount of
chaos a project can embrace and still be successful through
collaboration.
![Page 4: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/4.jpg)
chaos = changing market demands, evolving requirements, miscommunication, misinterpretation.
![Page 5: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/5.jpg)
waterfall and chaos don’t get along.
![Page 6: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/6.jpg)
waterfall wants order, predictability, known outcomes, benchmarks. Waterfall wants to
predict the future.
![Page 7: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/7.jpg)
and because we’re so in touch with the future,
we can anticipate how users will use the system six months from now.
![Page 8: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/8.jpg)
so let’s put together a 300 page requirements
document with all of the functionality we can think of.
![Page 9: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/9.jpg)
then we’ll throw it at the code monkeys, I mean engineering team, and project managers to build our system for us.
![Page 10: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/10.jpg)
the project managers, with their hierarchical command and control structure, will divide the work among disparate groups.
![Page 11: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/11.jpg)
these groups will work independently, reporting status back to the command and control center once a week or so.
![Page 12: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/12.jpg)
and three months later, when it comes time for the modules these groups built to talk to each other, they’ll find they
speak different languages and can’t communicate.
![Page 13: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/13.jpg)
so they’ll work 80 hour weeks for the next month to fix that little problem.
![Page 14: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/14.jpg)
oh yeah, and they’ll have to push out the
project deadline by two months to compensate.
![Page 15: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/15.jpg)
the system will finally be integrated, speaking one universal language, and the engineers will
have a celebratory beer.
![Page 16: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/16.jpg)
but then on Monday, when the business takes its
first peek at the new system, they’ll organize an
emergency meeting with the team leads.
![Page 17: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/17.jpg)
because the system won’t look like what they
envisioned five months ago when they predicted the future.
![Page 18: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/18.jpg)
and between now and then things have
changed, the business’ customers have demanded new features.
![Page 19: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/19.jpg)
at the meeting the project managers and engineers will
defend their positions, citing section numbers in the 300 page requirements document and saying “scope creep” a lot.
![Page 20: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/20.jpg)
concessions will be made, and the company will deliver a product that nobody wants to use.
![Page 21: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/21.jpg)
and they’ll do this after being two months late
and over budget.
![Page 22: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/22.jpg)
or we could use SCRUM.
![Page 23: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/23.jpg)
SCRUM divides projects into manageable
sprints.
![Page 24: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/24.jpg)
a sprint is a two to four week period where
something of business value is delivered at the end.
![Page 25: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/25.jpg)
the project team is involved from start to finish. Design, testing and coding can all happen on the
same day.
![Page 26: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/26.jpg)
testers, developers, marketers and product
managers intermingle becoming one big happy family.
![Page 27: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/27.jpg)
communication is constant.
![Page 28: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/28.jpg)
each day a 15 to 30 minute SCRUM meeting is held. Managers can watch, but they cannot talk.
![Page 29: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/29.jpg)
during the meeting, each team member answers three questions:– what did I do since the last SCRUM meeting?– what has impeded my work?– what will I do before the next SCRUM meeting?
![Page 30: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/30.jpg)
inter-departmental collaboration
+ frequent communication
= transparency.
![Page 31: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/31.jpg)
transparency = reduced risk, better product.
![Page 32: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/32.jpg)
requirements are delivered not in 300 page
documents but as user stories.
![Page 33: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/33.jpg)
user stories describe user experiences and have enough detail for SCRUM Masters to estimate
effort (size).
![Page 34: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/34.jpg)
A sample user story is “A consumer can
upload and play videos on the website”
![Page 35: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/35.jpg)
A sample user story is “A consumer can
upload and play videos on the website”
![Page 36: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/36.jpg)
The SCRUM team then adds detail to the user story during the course of the project and
clarifies ambiguity.
![Page 37: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/37.jpg)
User stories emphasize verbal communication.
![Page 38: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/38.jpg)
“Entrée comes with choice of soup or salad and
bread”.
![Page 39: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/39.jpg)
Does this mean:• Soup or (salad and bread) • (Soup or salad) and bread http://www.mountaingoatsoftware.com/article_view/27-advantages-of-user-stories-for-requirements
![Page 40: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/40.jpg)
The SCRUM Master has Authority over what details are permissible. His goal is to deliver at the end of the Sprint.
![Page 41: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/41.jpg)
He has no friends. He makes the business prioritize. He makes the developers compromise.
![Page 42: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/42.jpg)
At the end of the sprint the team shows off what they’ve done to the rest of the business.
![Page 43: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/43.jpg)
The stakeholders already knew what they were
getting and are happy.
![Page 44: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/44.jpg)
The developers are happy too because they built something the business can use.
![Page 45: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/45.jpg)
And everybody goes home to rest. Well at least until the next sprint begins...
![Page 46: Scrum](https://reader033.vdocuments.us/reader033/viewer/2022060119/558c9201d8b42a03438b4782/html5/thumbnails/46.jpg)