8 ms·
Imagined vs discovered tasks The way to really figure out what needs to be done is to start doing real work. https://basecamp.com/shapeup/3.1-chapter-10#imagi
by nivertech 6mo ago
Imagined vs discovered tasks
The way to really figure out what needs to be done is to start doing real work.
https://basecamp.com/shapeup/3.1-chapter-10#imagined-vs-discovered-tasks https://basecamp.com/shapeup/3.1-chapter-10#imagined-vs-disc...
imagined tasks == Jira
discovered tasks == Dark Jira
IMO, tickets for planned work are an anti-pattern. Tickets are good for reactive work: bug reports, support, etc. Use Kanban board for tracking them.
Planned work should be organically discovered from the plan by the developers (or agents) who will be implementing it, not assigned via Jira tickets by the project manager. Shape Up recommedns using Hill Charts for per-scope (vertical slice) progress updates.
- notpushkin 6mo agoThis. You always find out new stuff during the development. Nothing ever goes according to the plan. I have a favourite illustration of the way projects work, right at the top of this page: https://bureau.ru/about/fff/ https://bureau.ru/about/fff/ (The page itself is in Russian. Basically, it’s about the “flexible scope” principle from, you guessed it, Getting Real: https://basecamp.com/gettingreal/02.4-fix-time-and-budget-flex-scope https://basecamp.com/gettingreal/02.4-fix-time-and-budget-fl...)