How does design work relate to Pivotal Tracker?

361 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
361
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

How does design work relate to Pivotal Tracker?

  1. 1. How does design work relate to Tracker? Wednesday, September 25, 13
  2. 2. There are no design stories. Wednesday, September 25, 13
  3. 3. There are no development stories. Wednesday, September 25, 13
  4. 4. Stories represent work that yields business / user value. Wednesday, September 25, 13
  5. 5. Design work generates and defines stories. Wednesday, September 25, 13
  6. 6. Development work consumes and eliminates stories. Wednesday, September 25, 13
  7. 7. Design is making decisions • Researching in support of decisions • Thinking through many potential decisions • Getting stakeholders to agree on decisions • Making decisions explicit enough to be built Wednesday, September 25, 13
  8. 8. All development work is represented in Tracker. Wednesday, September 25, 13
  9. 9. Not all design work is represented in Tracker. Wednesday, September 25, 13
  10. 10. How does design improve velocity? • Design work unblocks development work. • Design work should answer questions about ‘how should this work’ so the developer doesn’t have to ask them. • Design work yields assets, so the developer doesn’t have to make or find them. Wednesday, September 25, 13
  11. 11. Design in the lifecycle of a story • Creation • Definition • Development • Acceptance / Rejection Wednesday, September 25, 13
  12. 12. Story creation • Anyone can create a story • Design work yields new stories Wednesday, September 25, 13
  13. 13. Story definition • Design work yields definition for stories • Responsibility for definition shared between designer and PM • Developers can define stories too, but it’s not a primary responsibility • Product owner should sign-off each story definition before developer starts it Wednesday, September 25, 13
  14. 14. Story development • Development work turns stories into working software • In-flight design tune-ups reduce rejections Rejections have moral, time, overhead cost Wednesday, September 25, 13
  15. 15. Story acceptance • Rejecting stories based on DEFINED design is legitimate. (Tune-up to preempt this) • Any increases in scope due to tune-ups or rejections should become a new story—no matter how small! • Making a designer/PM prioritize a tweak is sometimes enough to push it off. Wednesday, September 25, 13

×