The development team is working on a project that has fallen behind schedule. After 10 months, they have only completed the first release instead of the planned three releases. The customer is nervous about delays and the team is accumulating technical debt. The team acknowledges mistakes were made in analysis and estimation. They discuss the need to focus on building the right product instead of just completing tasks, and ensuring development aligns with the customer's needs through improved communication and presence onsite.

1. Product Over Project

2. Three TWers and CustomersInception

3. Prototypes

4. Master Story List

5. Estimates

6. Release Plan

7. First release in 10 months

9. After two months

10. Velocity is low

11. Team working harder

12. ..and is accumulating debt

13. Customer is nervous

14. Another month goes by

15. Finger pointing

16. Developers: A lot of this was not part of original scope

17. Customer: That is because of bad analysis

18. Analysts: Only if we were building stuff fast enough

19. Release in 20 months at current velocity

20. Estimation, Replanning and Contract Negotiation

21. Customer: You guys should fix bid it

22. Development Team: Looks like we have screwed up big time. We should work on weekends

23. TW: Guys lets make this happen

24. TW: We are giving discount

25. Almost five months!

26. Developer: Worried about quality of code

27. Can fill a whole newspaper with technical debt

28. QA: Worried about lack of automation

29. Analysts: Not keen talking to customer

30. TW: Do we have to give more discounts?

31. WHAT ARE WE DOING WRONG?

32. 1

33. We are not good at this game?

34. Every product is different

35. Software development is discovery process

36. Delivery is the only test of estimation

37. Everything else is just opinion

38. 2

39. Advice needs to be better than…Think out of boxBe focusedBe creativeStay commited

40. “Trying harder is not an improvement strategy” – Jason Yip

41. 3.

42. Planning (estimation) is important

43. Plans (estimates) are not

44. 4. Most Important

45. This is the wrong game?

46. What are we building anyway?

47. Why is no one talking about that?

48. Tail is wagging the dog

49. Project is defining the product

50. Don’t trust me

51. Look at your project status report

52. Listen to people in standup

53. So, what’s the proposition?

54. 1.Customer pays for software

55. 10Months is too long

56. Do Shorter releases

57. Find ways to do it. Don’t accept customer’s word for it.

58. Internal release if nothing works

59. Internal release should also meet all criteria

60. Customer Signed-off != Done

61. Focuses everyone on the next release

62. Its not how fast we are going

63. but… where we are going?

64. Effective over efficient-- Dan North

65. 2.Build the right thing

66. At the right time

67. Again..software development is discovery process

68. Yes, even for the customers

69. Need onsite presence to define the product

70. Not only to……to get story signed-offfor backlog creationfor feature estimation

71. Send best people onsite……instead of keeping them to keep velocity high

72. Creating a product which no one wants is worst kind of waste

73. Building things ahead of time is waste

74. Play the right game!