Too many software projects fail. Most often this is due to misunderstandings in between business and IT. To make that both business and IT understand each other better we need to bridge the gap. Agility might be the needed magic.
2. Gartner studies suggest that 75% of all US IT
projects are considered to be failures.
The solutions 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. They already managed
ages ago!
Image credits: http://www.flickr.com/photos/liberato/171610084/
So, why don’t we
manage to realize
something as
simple as a web
application?
4. Short introduction
40 Agile Blogger Coach Communication
Consultant Creative Director Dutch Engineer
Father Fun Gdaosk GOYELLO Honest
Husband Open mind Opinion Outsourcing
Partnership Peter Horsten Positive
Project manager Prince2 Social networker Sociologist
Software Trust Twitter University of Gdaosk
Web 2.0 Web applications Web development
6. Funky
reminds me
about a
concert by
Candy Dulfer.
What does it
mean to you?
Picture source: http://www.allaboutjazz.com
7. Funky
• 2b. Combining elements of jazz, blues, and soul
and characterized by syncopated rhythm and a
heavy, repetitive bass line.
• 3. Slang Earthy and uncomplicated; natural.
• 4. Slang a. Characterized by originality and
modishness; unconventional: "a bizarre,
funky [hotel ] dressed up as a ship, with mock
portholes and mirrored ceilings over the beds" (Ann
Louise Bardach).
Source: http://www.thefreedictionary.com/funky
8. Let’s Vote
Who has been
facing unhappy
clients while
developing
software?
Image source: European Parliament,
http://www.flickr.com/photos/european_parliament/3480264232/
22. Clearly specify the needs!
Still clients often change the
specifications on the fly because of
Market dynamics
But this is understandable in this
economy….
The only constant thing is CHANGE.
27. From TDD to BDD
As a Role
I require a Feature
To gain a Business Benefit
How we are implementing BDD at Goyello
28. Describe “user stories”
Write down the story
Make it clear and understandable for both sides
Make sure developers fully understand it
Prioritize together
30. 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
31. SCRUM
Three roles:
Product Owner, ScrumMaster and the self-organized team.
Three ceremonies:
Sprint planning meeting, daily scrum meetings, and sprint review meetings.
Three artifacts for prioritizing and tracking tasks:
Product backlog, sprint backlog, and a burndown chart.
Source: http://www.scrumalliance.org/learn_about_scrum
32. Find a good tool to manage the:
project
your developers
clients’ requests
and changes.
REDMINE
33. Clients have insight
Less e-mail, no information loss
Decreased response time
http://www.redmine.org/
36. Let’s treat the client
like a lady
and remember
the good old Polish manners….
37. “More freedom equals more
responsibility. If you do not
make choices, someone else,
somewhere else, will make
them for you.
And you can be sure that they
will not care too much about
your well-being.”
Funky Business, p 11.