12/16/2023 0 Comments Basecamp 3 review 2016![]() However a team decides to get it done during that time is up to them. We don’t measure efficiency, compare actuals vs. makes it very difficult for the whole team to see the whole picture. Splitting work and communication and management across separate tools/products is 1. When everything’s in one place, everyone knows where things are, where things stand, and everyone can be self-sufficient. No matter the role, everyone tracks work in the same place, communicates in the same place, etc. The designer on the team leads the project, but there’s a very close working relationship between designer and programmer(s). There are no hard and fast rules about this. Teams often change up after the cycle so everyone gets a chance to work with different people, but sometimes they stick together for a few cycles. Teams either coalesce around areas of interest, or we assign people to a team based on their preferences. Before a cycle begins, we ask each person what kind of work they’d like to do over the next six weeks. We think three is the ideal size for most things - complexity begins to increase exponentially beyond that. Everything we take on has to be done by a team of three, max. Either one programmer and one designer, or two programmers and one designer. Teams stay together for the full cycle.Ī team is two or three people, depending on the type of work. Small Batch projects are all done by one team. So if we take on two Big Batch projects during a cycle, we’d have one team working on one of the projects and another team working on the other project. Who does the work?Įach Big Batch project is assigned a team. No time is spent on big unknowns - we try to make sure all the big stuff is known enough before we get started. That way the six weeks is all implementation and execution. It has to happen before the work is slated to be done by a team. We don’t include planning in the cycle time - all the planning and consideration happens in the pitch. Not what can it be, but what does it need to be?īefore any project is included in a cycle, we’ve already figured out what we think the six week version is. It’s all about looking carefully at a feature and figuring out the true essence. We take the chisel to the big block of marble and figuring out how to sculpt, nip, and tuck a feature into the best six-week version possible. The secret to making this possible is something we call scope hammering. ![]() But we’ve come to discover that nearly everything important can be done in six weeks or less. Occasionally some things fall outside of this limit - deep R&D projects, brand new tech we’ve never used before, etc. We believe there’s a great six week version of nearly everything. Six weeks… What if something’s so huge it’s going to take longer? No brute force here, no catching our collective breath at the end. This isn’t about running all out as fast as you can, it’s about working calmly, at a nice pace, and making smart calls along the way. We also use this time to firm up ideas that we’ll be tackling next cycle. Once a six week cycle is over, we take one or two weeks off of scheduled projects so everyone can roam independently, fix stuff up, pick up some pet projects we’ve wanted to do, and generally wind down prior to starting the next six week cycle. To give you a sense of what kind of projects might fit into Big and Small, here’s an actual internal post announcing a cycle’s worth of work. ![]() We typically take on between 4 and 8 Small Batch projects in a six week cycle.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |