Realizing a solution is no longer enough
Imagine yourself a clever software developer, sitting in his room, working deep at night. For weeks, months, he's breeding on that one perfect solution. He codes like crazy, refactors, rebuilds. He wants it to be perfect. May be he showed it to some of his friends and they told him they like the idea. After a lot of hard work the solution is finally ready. Excited and full of expectations he introduces it to the market. Soon, all his effort will pay off, money will start flowing. Unfortunately, nobody seems to be interested in using the product and for sure they don't want to pay for it. What went wrong? How to prevent? During the lecture we will discuss how to cut this big salami into small pieces by using a lean development approach based on Scrum.
2. Gartner
studies
suggest
that
75%
of
all
US
IT
projects
are
considered
to
be
failures.
The
solu:ons
fundamentally
did
not
do
what
was
agreed.
Or
they
missed
deadlines.
And/or
came
in
over
budget.
Half
of
the
projects
exceeded
budget
by
200%!
WHY?
3. I’m a Dutch guy who fell
in love with Poland and …Picture source: Flickr.com
10. The Toyota way
• “Continuous
Improvement” (kaizen)
Challenging everything by
creating an atmosphere of
continuous learning and an
environment that embraces
change.
• “Respect for People“
Which is essential to create
such an environment
11. Manifesto for Agile Software Development
We are uncovering better ways of developing software by doing it
and helping others do it. Through this work we have come to value:
• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
That is, while there is value in the items on the right, we value the
items on the left more.
Source:
Agilemanifesto.org
12. Too many startups begin with
an ideafor a product
that they think people
want
13. The lean startup methodology
• Eliminate uncertainty
• Work smarter not harder
• Develop an MVP
• Validated learning
Source:
Theleanstartup.com
16. Scrum
is
an
Agile
soJware
development
framework
Scrum is an agile software development framework. Work
is structured in cycles of work called sprints, iterations of
work that are typically two to four weeks in duration. During
each sprint, teams pull from a prioritized list of customer
requirements, called user stories, so that the features
that are developed first are of the highest value to the
customer. At the end of each sprint, a potentially
shippable product is delivered.
Image source: http://news.bbc.co.uk/sport2/hi/rugby_union/7048733.stm
17. Three Scrum roles
• Product owner:
responsible for the
business value of the project
• ScrumMaster:
ensures that the team is
functional and productive
• Team:
self-organizes to get the work
done
18. Four ceremonies
• Sprint planning: the team meets with the product
owner to choose a set of work to deliver during a
sprint
• Daily scrum: the team meets each day to share
struggles and progress
• Sprint reviews: the team demonstrates to the
product owner what it has completed during the sprint
• Sprint retrospectives: the team looks for ways
to improve the product and the process
19. Three Artefacts
• Product backlog: ordered list of ideas for
the product
• Sprint backlog: set of work from the
product backlog that the team agrees to complete
in a sprint, broken into tasks
• Product Increment: required result of
every sprint. It is an integrated version of the
product, kept at high enough quality to be
shippable
22. Contact details:
@ peter.horsten@goyello.com
8 http://goyello.com
8 http://blog.goyello.com
8 http://petersopinion.com
http://twitter.com/PetersOpinion
DEDICATED TO YOU
Thanks for your attention!
Feel free to contact and follow!
Or ask questions today, I don’t bite ....
Goyello Sp. z o.o.
Al. Grunwaldzka 472
80-309 Gdansk