rough draft - sanctuarycomputer/home GitHub Wiki

Full Scope Project Planning/Backlog Creation/Story Writing Workshop

Prior to sprints we should have full scope project planning. We can create tickets for all story points listed in the signed scope that will initally live in the backlog. We can attribute user stories to these tickets which will help us understand the task and flesh out smaller tickets for sprints. This process will help us stay within our deadlines by working within our quoted estimates. It will also monitor where we underestimated or were thrown off course by an unexpected complexity or aversion to building something not scoped.

User Story Example: As a (type of user), I want (some goal) so that (some reason). e.g. As a customer, I want to change my delivery address, so that I see the menu items at the location closest to me.

Individual Spring Planning

Prior to weekly sprint planning:

• Ella: Will review blocks, contact blockers, and calculate unblocked dates
• Devies: -Should review tickets & PRs and move to appropriate status column -Should review last sprint's tickets and make note of those with complications and incorrect estimates

Sprint Planning Process

• Review previous sprint's burndown rate
• Review previous sprint's tickets with complications
• Asses amount of points we can achieve in this sprint
• Definition of done - esp on first pass, how far do you go with it? -- keep each ticket as contained as possible, when you feel like oyure gonna blow it out just push out what you got and create new tickets

**To Think On: **

• Better ways of merging pull requests - set a timer/slack reminder to check for pull requests)
• better ways of ordering things
• Setting vocab up front

Guidelines: Talk it out, talk it out, if you're not sure how you're gonna tackle ticket, lets talk it out Let's not break until we're totally done. If we gotta we eat or whatever we should agree to meet back at a certain time.