Contract and procurement should change according to current Agile situation. We'll share and discuss how Agile Contract and Procurement should not be a impediment in Agile.
20. We are in Complex Problem, perhaps what I
present is just your trigger or inspiration.
Maybe it is or it is not your
“good practice” / “best practice” guide
Because every organization have their own
Path of Agility
24. Business are full of RISKS
How much do you understand /
trust your customers ?
How much do your customers
know about / trust you ?
How much do we understand
ourselves?
So, Contract Need for
PROTECTION Pi S Hung
27. “The Guardians” usually ...
Trained to think the UNTHINKABLE
Talyorism
Think Software Projects as “A Series of Planned
Activities”
Don’t like surprise and expected everything is
relatively predictable
28. Traditional Contract
All requirement and feature
under request, specific detail
in contract. And usually from
imagination.
Fix Schedule - Fix Price - Fix
Scope
Collaboration doesn’t exist
Quality is usually as variable
Chance failure is high
54. 9 Agile Procurement Concept
1. It is outcome based
2. Relationship focus
3. Flexible Sourcing (Meeting before choosing)
4. The team works with suppliers at the beginning.
5. Solving problems at the source (Proactive than Reactive)
6. Negotiate the contract during the sourcing process
7. Eliminate anything that will not affect the outcome
8. Cross Functional Team
9. Always Challenge Status Quo
73. We are in Complex Problem, perhaps what I
present is just your trigger or inspiration.
Maybe it is or it is not your
“good practice” / “best practice” guide
Because every organization have their own
Path of Agility
Silahkan Japri kalua ada pertanyaan lebih lanjut, biasanya materi agile contract itu 1 hari. Tapi ini di compress jadi 1 jam. Ini ada analisa contoh2 kontrak yang agile & tidak.