I work for a very small organisation - two developers, one part-time support person, and a board of trustees (we’re a charity). It’s transitioned from a side-gig by the founder (the other developer) 9 years ago, to an incorporated charity a year ago. We’ve been using a vague Scrumban approach since I joined full time 18 months ago with mixed success, and now we’re keen to have a go at Shape Up as it seems to fit a lot of our needs.
I appreciate the advice in the appendix to follow principles vs specific methods - e.g. some of the formalities don’t make sense with two people (our trustees provide high level guidance and accountability, not specific project input so aren’t relevant to this level of day-to-day life). However, I think some of the formalities could really help us, e.g. the distinction between a cycle vs cool down would help us to focus on a project whilst knowing we have the time to deal with those bugs or edge cases.
I guess I’m looking for any advice or just stories from other small teams that have had a go “Shaping Up”. What has worked for you? What hasn’t?
An additional point here is that primarily I am the web developer and primarily my colleague is the mobile developer. These are often quite distinct domains for our product - the apps have a large set of customers whilst the website has a much smaller, different set of customers. Sometimes our work dovetails together and requires work on both platforms, but sometimes it is really quite separate. Is having us both working on separate projects, in effect as separate teams, viable with Shape Up?