in

Agile Israel

Israel's first Agile Development Community

Browse by Tags

  • Sprint Planning versus Version Planning

    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 internal planning External value (features your customers...
  • Should you allow changes during Sprint?

    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 “we will be Agile enough to allow you to change...
  • Why tracking Actual Hours is so imperative?

    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, I believe that tracking Actual Hours is imperative...
  • Story Points over Ideal Days?

    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 any meetings, phone calls or people bothering you...
  • Why should you strive for moving Features to done?

    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 accomplishment), striving for done features will...
  • Estimating Features: options, context and God

    “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? Although there are no recipes for estimating successfully...
  • Planning your Sprint

    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, and there are many moving parts. You need to please...
  • Visibility over Progress

    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 days are left or whether or not you’re closer...
  • Adjusting big Features to Sprints

    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 Features over time. User Stories as execution...
  • Beautiful Code?

    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 great painters talk about beautiful colors or...
Page 1 of 22 (211 items) 1 2 3 4 5 Next > ... Last »
Copyright 2007 Roy Osherove