● How to get funding
● How to keep every stakeholder happy
● How to actually succeed
Many aspects in IT projects
● The end user
● The manager
● The project team
The Three Stooges
We have widespread use of Agile project
● Is iterative
● Brings value early on
● Makes developers talk with the customer
● Shows problems and actual needs early
● ... so you can react to them
helps projects to succeed
Which makes customers happy
While making the developers look good
Most importantly Agile
Not every project uses agile...
One downside there is
The managers with the money.
And it is because of these
Because they don't get Agile
"I don't get it?
6. Use happily ever after
They have milestones and easy to
But they DO understand Waterfall
Only gives money to projects he can
Ok. So you have to choose Waterfall.
You get the funding and start doing your
project using Waterfall...
The person with the money
Read more about WaterfaIl
● "Agile success stories": 4 400 000
● "Waterfall success stories": 368 000
o -> Mostly starting by phrases like:
"Report says Agile is more successful"...
"Where is Waterfall failing us"...
1.Is easy to understand and
sell to the managers
2.Actually enables the
project to succeed
So we need a project model that
Combining in the easy understandability of
Waterfall and the power of Agile methods.
The Fountain Project Model
-> 1st step is Deployment
Wow, isn't that kind of hard?
Empowered by the Talaskivi
-> Planet Earth on the first day
A puny working software on the second day
Should be doable.
● Apply Fountain Project Model to web-
projects where you as a developer
already know on which technology would
● Select the technology stack which is the
most familiar to the developers/your
Lets set some boundaries
People have bended different systems to
do something that the system really wasn't
meant to do...
You can do anything with
everything in IT-world
You must do different things with
● The end user: provide working software
● The manager with the money: provide
● The develoment team: get out of their
As a project manager...
2. Customer/end user figures out the next 3
most important features
3. Develop (BDD, TDD, whatever suits you)
and deploy again to the preview-site
4. Talk to the customer again, 3 next most
5. Develop until customer is happy enough
The stages of springing a
You can make it look like this for
1. Stage ONE
2. Stage TWO.
3. Stage THREE
4. Stage FOUR
● You can show him a "Gantt-chart" of
different phases of the Project
● He can feel pleased with himself as he
● If some dates are off, its okay -
remember - IT-projects tend to fail.
● But eventually this project actually
succeeds and the Manager gets more
Benefits for the Manager
And this is how it actually looks
for the Customer
2. Development A.
3. Release A
4. Development B.
5. Release B.
Start getting profit
for the first set of
See the first version
of the service and
define 3 next most
See the changes
in the demo site
as things evolve
Customer is already getting value from the product
● On the second day of the project, the
customer gets a working site.
● It's easier for the customer to see what's
missing than to explicitly define what
should be added
● The customer can then point and
comment on things
● In the end (or beginning!) the customer
gets a working system!
Benefits for the Customer
And this is how it looks like for
● Developers get the funding!
● Developers can easily discuss with the
customer using the demo site
● Developers can focus on only 3 things at
● Don't have to develop features that
nobody uses at the end
● Satisfied customer, satisfied CEO
-> a bonus?
Benefits for the Developer
...if not a bonus, at least the feeling that
you have done well.
When the Fountain is so big it makes a
rainbow with the Sun shining behind it.
When is the project ready?
DO not apply in Russia. They don’t like
● Talk to the end users - show and tell,
and let them tell you
● Use Agile methods in the actual
● ...and disguise them when talking to