Deadlines and Agile might seem like they don’t fit into the same workflow paradigm. The reason?
Strictly speaking, they don’t focus on strict long-term deadlines, but focus on short-term pace, and 1–3 weeks deadlines. Agile requires teams to conceive of finishing projects with a higher focus on market feedback and customer’s real needs.
So, what is a deadline in fact?
Deadline is a narrow field of time, or particular point in time, by which an objective or task must be accomplished.
Let`s see again a difference between traditional and agile software development:
What’s so wrong with deadlines?
Most people think of deadlines as fixed and 100% predictable, but in reality, they are imminently changeable.
Things happen — such as market and end-users feedback, competitors strategy impact, different level of risks, or budget changes — that make it impossible for teams to guarantee achievement of carefully planned long-term deadlines. If deadlines are absolutely inflexible, too, teams might feel like they have to cut corners, completing a product that isn’t quite up to the standard that was expected.
How does a team think about implementing Agile without long-term fixed deadlines?
Instead of focusing on setting strict deadlines, Agile teams instead consider project goals and problems that need solving. They use short iterations (sprints) to achieve small wins and provide potentially shippable product increment with a constant pace. From there, teams can ensure they are making the right kind of progress — working on what they need to be doing to move towards project completion.
How do teams ever finish projects?
Getting rid of long-term deadlines and detailed plans can be scary. But even without long-term plans, you won’t be left adrift. Here are some of the methods Agile teams use to track progress:
- Sustainable Pace. Agile differs from other methods of management because it doesn’t value quick bursts of effort followed by downtime. Instead, Agile suggests that developers should maintain a constant working pace — indefinitely.
- Transparency — “significant aspects of the process must be visible to those responsible for the outcome. Transparency requires those aspects be defined by a common standard, so observers share a common understanding of what is being seen.”, — Scrumguide
- Predictability of teams performance that expected to be similar in every sprint (velocity) that allows making long-term planning.
- Estimation practices like planning poker that combine the three most common techniques for estimating: Expert opinion, Analogy, and Disaggregation into an enjoyable approach to estimating that results in quick but reliable and accurate estimates.
How can my team improve estimations and predictability?
Estimating accurately can often be a challenge. For example, Ciklum’s Project and Process Management unit helped the Xanadu Consultancy, a software development, and operational support firm, improve the accuracy of estimations. The main idea was to use the Story points for high-level estimation of User Stories in the backlog. Also we have used hours/ideal hours for estimation of subtasks/tasks taken to the Sprint. This approach allows making long-term planning fast and achieve a good level of accuracy. Thus, Xanadu Consultancy have reached the transparency inside the Sprint on a daily basis. After an introduction of the above mentioned estimation approach and a lego simulation workshop, Xanadu’s team were able to understand the importance of predictability in team’s performance and to decide on estimations, long-term planning, as well as develop a Releases Roadmap (i.e., the plan for how the processes or solution will evolve over time).
Like Xanadu Consultancy, many teams have difficulty implementing Agile’s more non-conventional time processes. If you’re struggling with the accuracy of estimations, handling spikes, tracking progress within the Sprint and mitigating risks in case of underestimation, do not hesitate to contact Ciklum to get assistance!
Originally published on Ciklum Blog on February 22, 2017.