search

Lever-age / leverage

Empower citizens of Philadelphia to use campaign finance data when making informed decisions about who they donate to, who they support, and who they vote for.
http://leveragecampaignfinance.org/
20 stars 10 forks source link

Put together the process that a feature follows from submission to resolution/incorporation into the project #5

Closed sergeantbacon closed 8 years ago

daksb commented 8 years ago

Anyone could create a user story/use case such as new feature, bug, enhancement to existing feature, data issues, IT issues, documentation and put them in the backlog.

I propose that we should have a shorter sprint/iteration. Each cycle would last about 2-3 weeks. Each sprint team should execute following steps:

  1. Team grooms an iteration backlog - Decides on what goes into ready to be worked/to-do list based on priority etc.
  2. A story can be split into multiple tasks if necessary, team member self-assigns task and starts to work on it if member encounter obstacle, she/he can reach out to the team via slack or other channel
  3. Team should meet each week to go over their progress and/or to discuss impediments
  4. At the end of each iteration, we demo our work, then we could have retrospective

We can continue to go thru this cycle until our product is stable and production ready.

Please feel free to add if I missed anything.

sergeantbacon commented 8 years ago

@daksb: That's a solid start.

Our challenge now is to adapt this base framework to accomodate the characteristics of our project and team. Off the top of my head, two of those characteristics are

In particular, let's consider how we can maintain a tidy process but minimize the amount that one person's absence can limit the flow of work. It's important that anyone looking to pick up a new item to work on can do so without waiting for interaction from someone in the team that's coordinating the work. I think this relates to your step 1: grooming the backlog.

lottspot commented 8 years ago

I think this issue actually touches on some ideas that are really relevant to where we are right now with the MVP launch. We should roll this discussion into #28 in order to consolidate the conversation