Thread by @peteryared

Why does software need so many people and take so long compared to the recent past? Let's compare! 🧵 cc @realGeorgeHotz

Process before 2010:
1. PM adds ticket to Kanban board "Add a date picker to the date fields"
2. UI Engineer picks ticket, finds 3 suitable components, emails PM which do you like
3. Date picker implemented
4. QA team make "pick a date" test plan & QAs
5. Ships in next release

Process after 2010:
1. New ticket in Jira "Add a date picker to the date fields"
2. Ticket triage with product managers and architects, architects select date component to use
3. UX team designs all possible interactions in Figma
4. Scrum meeting where tickets are selected

5. Product manager writes detailed ticket with definition of done
6. Estimation where team estimates time to implement date picker
7. Junior UI Engineer assigned ticket.

8. Bugs in the date picker component -> emergency Slack -> ticket kicked out of sprint -> back to Step 2.
9. Date picker component can't implement all the UX interactions in Figma -> emergency Slack -> ticket kicked out of sprint -> back to Step 2

10. Sprint reconciliation where all of the above is discussed in excruciating detail and passive aggressive tensions allegedly resolved between product managers, architects, UX, engineer, with conclusion to have more meetings at each above step so this doesn't happen again

11. Ticket delayed due to new priorities
12. Junior UI engineer complains to HR about terrible onboarding and mentoring processes
13. External scrum coach brought in to improve process and communication
14. Management: "How can it take so f'ing long to add a date picker?!?!?"

I'm sure I missed some critical steps, add your faves!