4 ms·
> Assign agents the biggest piece justifiable This has always worked like this. Let the person working on the ticket discover the implementation details, break
by notpushkin 7mo ago
> Assign agents the biggest piece justifiable
This has always worked like this. Let the person working on the ticket discover the implementation details, break it down into tasks, maybe delegate some after they’ve dipped their toes and know how to split it into sub-tasks better.
And of course, obligatory Shape up mention: https://basecamp.com/shapeup https://basecamp.com/shapeup
- gavmor 7mo agoCan you narrow down your Shape Up citation?
- nivertech 7mo agoImagined 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 7mo 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...)