Embed Size (px)
DESCRIPTION
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.
Citation preview
How to manage
software development
in a Funky way?
Copyright © 2009 GOYELLO
University of Gdansk, IT ACADEMIC DAYS
December 9, 2009
Peter Horsten, Goyello
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?
They already managed
ages ago!
So, why don’t we manage to realize something as simple as a web application?
Image credits: http://www.flickr.com/photos/liberato/171610084/
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
Short introduction
Feel free to interupt
Don’t waittill the end!
You mightforget
Image source: http://www.flickr.com/photos/mr_shanab/2712194064/
© All rights reserved.
Funky
reminds me
about a
concert by
Candy Dulfer.
What does it
mean to you?
Picture source: http://www.allaboutjazz.com
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
Let’s Vote
Who has been
facing unhappy
clients while
developing
software?
Image source: European Parliament,
http://www.flickr.com/photos/european_parliament/3480264232/
Copyright © 2009 GOYELLO www.goyello.com
Potential software development Issues
Exceeding the budget
Not meeting the deadline
Clients are not happy with the delivered
functionality
“It’s not what they imagined”
Is what they buy
the same thing
you sell?
Put yourself in your
customers' shoes.
Copyright © 2009 GOYELLO www.goyello.com
The consequences
Unhappy clients
Bad PR for IT industry
Yet another IT project
that failed
Copyright © 2009 GOYELLO www.goyello.com
The reasons (not limited)
•Poor planning
•No time for design
•Unclear goals and objectives
•Lack of understanding
•Objectives changing during the project
•Unrealistic time or resource estimates
•Lack of executive support and user involvement
•Failure to communicate and act as a team
•Inappropriate skills
•Lack of Quality management
How IT people tend to treat a client
How clients think about IT people
“…a bunch of
nerds…”
“…they can only
communicate in
techno babble….”
Business and IT should be aligned
Business IT
Strategic
Tactical
Operational
We need to close the gapin between
BusinessandIT
It should beBusiness with IT
Too often we follow
conventional methods
But be aware! Clients don’t specify their
requirements very clearly
Copyright © 2009 GOYELLO www.goyello.com
Or…in this case
You hope for this…
And this is what
you get
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.
Let the client
telltheir story!
We need more flexibility, more Agility
Now let’s add some Funk into the project mangement
Agile
SCRUM
BDD
TDD
FDD
RUP
Extreme programming
Innovation
Copyright © 2009 GOYELLO www.goyello.com
Project approach at GOYELLO
Intake
Kick-off
Implementation: Sprints, daily Scrums,
evaluations
Deployment
From TDD to BDD
As a Role
I require a Feature
To gain a Business Benefit
How we are implementing BDD at Goyello
Write down the story
Make it clear and understandable for both sides
Make sure developers fully understand it
Prioritize together
Describe “user stories”
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
SCRUM
Source: http://www.scrumalliance.org/learn_about_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.
Find a good tool to manage the:project
your developersclients’ requests
and changes.
REDMINE
Clients have insight
Less e-mail, no information loss
Decreased response time
http://www.redmine.org/
Copyright © 2009 GOYELLO www.goyello.com
Have kick off meetings over beer in an informal
atmosphere
Agility needs a mind shift
Are you going to change your attitude?
Let’s treat the clientlike a lady and remember the good old Polish manners….
“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.
www.goyello.com
Feel free to contact and follow!
Or ask questions today, I don’t bite ....
Thanks for your attention!
Contact details:@ [email protected]+48 664 48 68 48 http://goyello.com http://blog.goyello.com http://petersopinion.com
http://twitter.com/PetersOpinion
Copyright © 2009 GOYELLO
