Two options to accomplish a goal, the first one and the last one. That’s how we discuss it, two options. We can implement the former or the latter and see how it goes. If you are faced with these two choices, there is always a third, a fourth, a fifth, somehwere between former and the later – that’s where your answer lies.
Manager’s don’t estimate workloads. They challenge the estimate, playing devil’s advocate, poking holes where they see them, but they do so with the goal of helping the developer get better at the task in being more precise. They don’t do it to knock them down or crunch their numbers furthers. There is no mythical person month that makes work go faster. If you want it done right, you put in the time and you get…
The problem with every pilot is always the date. Always has been, always will be, primarily because when we agree on a pilot we are doing it off of what we know at a certain point in time before the pilot begins. We think we know what we are going to build and be able to get done. By that date. As you approach the pilot, you realize you might not get there – either…
So am I. There are days I miss being stuck in traffic and listening to radio banter or my favourite podcast or simply going into auto-pilot as I make my way into the office. I’ve always enjoyed being remote with a sprinkling of on-site days to revitalize and refresh the memory – “Oh, that’s why we’re doing this.” This is a great convo on Remotely Prepared we’re having on that old commute. https://www.upsidedownoffice.com/podcast/the-remote-commute
In agile, there is a concept called “Capacity”, drilled down further to be in a per sprint cycle – “Sprint Capacity”. A sprint is a block of time in which you set out to accomplish a particular task, generally 2 – 3 weeks, capacity is the allocation you have to complete a certain amount of work in that time period. A typical developer, dedicated to one sprint (let’s say it is 2 weeks) might be…