littlebits / team-workflow

The workflow used by software teams at littleBits

team-workflow

The workflow used by software teams at littleBits

team-workflow's Issues

Consensus based decision making process

Creating a discussion space / voting system for some decisions might be a great way to resolve conflicts. (ie python vs javascript vs go)

Rename project to littlebits-flow

<system-name>-flow is standard terminology for this domain. I also don't want colleagues at littleBits in other pods to think that we think we know best for their workflows. I'm only concerned about getting our slice right, and that fits well within the *-flow world.

Examples:

Gitflow
Github-flow

eslint changes

• https://github.com/littlebitselectronics/cloud-control/pull/194/files#r25888068

What will we do with this repo?

I would like to have a general consensus from our cloud software team about what we will use this repo for.

Who

I have chosen to limit the scope to the cloud software team because we are the smallest, least codified, most lean, and most dynamic (by number of discrete projects) software team at littleBits; we are the ideal trial group.

What

I propose that this repo be the place for us to openly discuss, codify, evolve, and reference our workflow.

1. "Openly" means that we share our thoughts in the public domain, welcoming external participation and also gladly influencing the external world.
2. "Discuss" means that we all share responsibility for workflow we choose and all final decisions are based on consensus.
3. "Codify" means that workflow choices manifest in written form. If its not written it does not count.
4. "Evolve" means that no workflow choice is final. We will always be open to discussing new ideas, revisiting old ones, and reevaluating our current workflow.
5. "Reference" means that this place will be how we will onboard new hires and contractors. We expect that by merely referencing this place people should be able to know what to expect and what the expectations are of them. Further, we think that be doing this "openly" others outside littleBits may come to reference this too; should they find it useful.

---

This is my goal with this repo. I agree with it. Check off your name once you do too, and/or discuss!

• @jasonkuhrt
• @stresslimit
• @sssyed

Once we have consensus, close this issue.