How and why we do projects at ASPgems. Delivering Agile solutions since 2006. More than 11 years, more than 200 projects.

1. Projects at ASPgems
@agustincnc
agustin@aspgems.com

2. @agustincnc@agustincnc
Complex

3. @agustincnc
Unique

4. @agustincnc@agustincnc
And now.... ?

5. @agustincnc
Doing a project on
time and budget is as
easy as walking over
water

6. @agustincnc
Only one requirement:
water and specs frozen

7. @agustincnc
Define goals

8. @agustincnc@agustincnc
Build a model

9. @agustincnc@agustincnc
Build a plan

10. @agustincnc@agustincnc
Plan resources

11. @agustincnc@agustincnc
Identify risks

12. @agustincnc@agustincnc
Anticipate problems

13. @agustincnc@agustincnc
Have alternatives
ready

14. @agustincnc
ResourcesTime
Features
Choose two

15. @agustincnc
Manage progress
Spent
Planned
% =

16. @agustincnc
Manage progress
Spent
+Spent Needed
% =

17. @agustincnc
Manage

18. @agustincnc@agustincnc
Change control

19. @agustincnc
“Stats”
http://net.educause.edu/ir/library/pdf/NCP08083B.pdf

20. @agustincnc
Why?

21. @agustincnc@agustincnc
Lie
•You think you
know what you
want, but
•You just have an
approximate idea

22. @agustincnc@agustincnc
Future changes
• The market changes
• Your ideas change
• Technology changes

23. @agustincnc
The plan does not work

24. @agustincnc

25. @agustincnc
You can’t plan

26. @agustincnc
You can’t plan

27. @agustincnc
The plan does not work

28. @agustincnc@agustincnc
Increase control
• Less resources for the project
• Control reduces flexibility
• Project minutes, documents no
one read
• Cost of control and
documentation

29. @agustincnc@agustincnc
Communication
From your head to your
voice
From what you speak to
what I get
From what I get to what I
want to build
From what I want to build
to what I build

32. @agustincnc@agustincnc
My name is Agustín and I am
alcoholic

33. @agustincnc
In our world

34. @agustincnc
Risk
Low tecnichal Risk High tecnichal Risk
LowBusinessRiskHighBusinessRisk

35. @agustincnc
The web will always be a little bit broken
Tim Berners Lee
http://www.hyperorg.com/misc/nprbroken.html

36. @agustincnc
Release early, release often
If everything is fine, probably you are late

37. Error cost

38. Error cost

39. Error cost

40. @agustincnc
What you don’t know is more
relevant that what you know

41. @agustincnc
Maximum affordable loss

42. @agustincnc
Engineering
vs.
Craftsmanship

43. @agustincnc
ResourcesTime
Features
Choose two

44. @aspgems
Traditional vs Agile
Features Resources
Time
Estimate
Fix
FeaturesResources
Time

45. @agustincnc
Change question
How long and how much does it
cost?
Which is the best project I can do in
the time I have with the resources I
have?

46. @agustincnc
Change principles• Collaboration
• Less is more
• The user rules
• Minimum viable project
• Uannimity
• Don’t build models,
build the real thing

47. @agustincnc
Collaboration

48. @agustincnc
Less is more

49. @agustincnc
The paradox of choice
Barry Schwartz

50. @agustincnc5
positive effect of # options
-Satisfactionlevel+
- number of options +

51. @agustincnc51
negative ones
-Satisfactionlevel+
- number of options +

52. @agustincnc52
total
-Satisfactionlevel+
- number of options +

53. @agustincnc
If the user says it is broken, then it
is broken

54. @agustincnc
Minimum viable
project
Aim for the
smallest
possible project

55. @agustincnc
unanimity

56. @agustincnc
fucntional darwinism

57. @agustincnc
Cost vs. Benefit
Less Cost More Cost
LessBenefitMoreBenefit

58. @agustincnc
Iterate

59. @agustincnc
Lessons learned

60. @agustincnc@agustincnc
Agile is not technology

61. @agustincnc@agustincnc
Top management

62. @agustincnc
http://vimeo.com/29719577

63. @agustincnc
http://www.slideshare.net/sgreene/salesforcecom-agile-transformation-agile-2007-conference

64. @agustincnc
Can’t do both

65. @agustincnc
Thanks!!