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