InfoQ Homepage Sprint Planning Content on InfoQ
Articles
RSS Feed-
/articles/estimation-skills-planning-game/en/smallimage/WW0e1GkI-1650537510392.jpg)
Improving Your Estimation Skills by Playing a Planning Game
Underestimation is still the rule, rather than the exception. One bias especially relevant to the estimation process is the planning fallacy. This article explores the planning fallacy and how we are vulnerable to it. It explains how you can reduce your vulnerability to this fallacy through playing a planning game that has been specifically devised to help mitigate it.
-
/articles/metrics-team-dependability/en/smallimage/metrics-team-dependability-s-1609150308847.jpg)
Key Sprint Metrics to Increase Team Dependability
What are the questions you should be asking and what behaviours should you be measuring within your Scrum teams in order to improve overall dependability and delivery efficiency? We explore how you can transform your Sprints into the building blocks for success and ensure you can continue to meet (and even surpass) long-term user and business expectations.
-
/articles/sprint-product-goals/en/smallimage/Product-Goals-not-Sprint-Goals-l-1576514518297.jpg)
Product Goals, not Sprint Goals
There is a myth that Sprint Goals are a way to focus Scrum teams towards a common purpose, and without Sprint Goals, teams would end up building a disparate list of Product Backlog Items, every Sprint. This is in fact not only untrue, the reality is the exact opposite, that Sprint Goals are in fact a distraction and would only deliver parts of Product Goals.
-
/articles/user-stories-placeholders-requirements/en/smallimage/agile-logo.jpg)
User Stories Are Placeholders for Requirements
It can be difficult to change from a Waterfall approach where ‘business analysts write big requirements up front’ to the Agile practice in which requirements are prepared ‘just in time’, and are the responsibility of the entire team. The secret to success in Agile is ruthless management of scope.
-
/articles/use-case-20-slices-Dutch-Railways/en/smallimage/logo-agile.jpg)
Keeping Development ‘On Track’ with Use-Case Slices at Dutch Railways
How can you get from high level system requirements (features/epics) to the right level of specification to enable agile development? This article describes how Dutch Railways made the transition from large use cases which were completely written before development, to “Use Case 2.0” and why this helps them to deliver apps faster and with the right business value.