-
Should you start with planning your sprints and then see how it fits your versions? Maybe start with versions and understand how your sprints look like? Maybe planning versions by themselves is enough? How do you start? Decouple external planning from...
-
Sprint is a planning unit , keeping it stable during that time allows a pretended piece of mind for the developers from marketing/product ever-changing demands. So it feels anyway. We developers signed up a virtual contract with our product teams saying...
-
After bashing prediction systems, claiming that measuring performance of your teammates to predict release dates or personal behavior is inherently wrong , you might deduce that I meant “measuring Actual Hours is pointless”. On the contrary my friend...
-
Many teams going into Scrum, have internal debates around whether or not moving to Story Points or sticking with Ideal Days. It seems that there is a lot of personal feelings involved. Ideal Days – what is it all about? Just imagine a work day without...
-
If Sprints are not execution unit , what is the rush of moving Features to done as soon as possible during a sprint? Why should you care about it if you’re not limited by end of sprint deadline? Other than the fact that done is fun ™ (obvious sense of...
-
“We need to support registration in the application. Here are some details, how many days to develop?” -- Where should you start from? Should you simply throw a number? Maybe read it first and use your gut feeling, your experience? Is there a trap here...
-
With a given time window and people, how much can you pull off? Many managers are requested to offer a plan. Knowing how much you can actually deliver is one of the toughest question managers need to face with. It’s too elusive to measure it correctly...
-
After talking quite a bit about how to break a Feature into tasks and avoiding leftovers , I would like to address the natural habit of what I call “blindly moving forward”. How often do you find yourself after 3 days of coding, still unclear of how many...
-
Many times when picking Features as execution unit, it’s hard to fit a big Feature into Sprint. This always cause the feeling of Features is too big as an execution units, leading some organization to prefer User Stories over Features, wrongfully neglecting...
-
I remember enjoying Jeff Atwood’s (aka Coding Horror) post about “code isn’t beautiful” . It took me a while explaining to myself why people are chasing after “beautiful code” so much. Why people are so passionate finding or forming beautiful code? Should...
-
Once you decide how to break a feature into tasks , it’s crucial to make sure you don’t leave any leftovers as part of the breakdown. Feature breakdown must include each and every task to make it a complete unit you can deploy as part of a version . Completeness...
-
One of your responsibilities as a developer or team leader is to make sure you’ll be able to shine over time by constantly building confidence . This is why I strongly believe in maintaining a list of technical Features as part of your backlog. These...
-
There are many ways to take a Feature and break it into workable unit of Tasks . Measuring “breakdown quality” is being ignored most of the time, as it’s very elusive to define “good breakdown”. The ability to break something into smaller pieces is one...
-
One of the responsibilities of a great execution team is to make sure they will deliver in great speed and great quality, over time. “It’s a marathon, not a sprint” might be a confusing statement if you’re actually using Sprints in your development process...
-
User Stories became very trendy when Scrum became popular due to its smaller abstraction level ; this made it possible to break big Feature and adjust its pieces into a single Sprint. I think this was taken too far, where User Stories sometimes completely...