Scope down a feature #12
Description
Link to the coursework
https://workshops.codeyourfuture.io/#goblin-breakdown
Why are we doing this?
Your project is probably getting out of hand about now. It can be challenging to efficiently manage the work of multiple people on one codebase without each blocking the other or overwriting your work. The most difficult and valuable skill a developer can build is the ability to deliver simple, well-structured features that are fairly self contained. A good way to do this is to scope down your tickets.
Read over your refined tickets.
(If you don't have any left, move to the Backlog.)
❓ Is the ticket too big to do in one day? It definitely needs to be broken down into multiple smaller scoped features.
❓ Does the ticket contain two different features, functions, or components? It's two tickets! Break it down.
❓ Will the ticket require many changes across five or more files? Break that ticket down please!
Maximum time in hours
1
How to get help
If you are stuck on how to scope down your tickets, ask in Slack. Remember to explain your problem clearly, with links. If you did not do the Goblin Breakdown workshop, try it now.
How to submit
Work directly on your team planner.