In team refinement sessions, conversation and collaboration are key. As a Scrum Master, I’ve witnessed hundreds of hours of refinement sessions. What I observe, across a wide range of teams, is often a member of the team (most likely a business analyst or product owner/manager) gathers requirements from a team on the fly, sharing their […]
Author: Rachel Hanley
A few months ago my husband decided to grow some Japanese Sakura trees. He went through both the stratification and germination steps and about 5 weeks ago the seedlings were ready to be planted. Maybe it is because I have been working from home and walking past the pots a good few times everyday, or […]
Categories
Shu ha ri
A Learning Model is a device designed to guide you through the process of acquiring and applying a specific set of information Learning models can provide insight into where your peers are in their own agile journeys Different individuals will acquire skills at different rates Shu ha ri Originated in ancient Japan Designed to describe […]
Categories
Velocity
Velocity is a measurement of how much work a team can get done in a sprint. At the end of the sprint the team’s “Velocity” can be calculated by adding up the estimates (in our case story points) for those items that have reached ‘done’. We can track Velocity over time from one sprint to […]
Story points are designed to give an indication of complexity. Their purpose is to help estimate a task. They also help to calculate velocity and aid release planning/forecasts. Scrum does not recommend any particular estimating approach but arguably the most common approach is story points (I believe its origins are linked to Xtreme Programming). The […]
Muda “waste” Mura “variation” Muri “overburden”
A product backlog is an ordered list of all features, functions, requirements, enhancements and fixes that constitute the changes to be made to a product in future releases. Each item is called a product backlog item (PBI). All items should include a description, value, order and estimate. Items can also be defined as Epics and […]
The more specific a product backlog item is, the more efficient a team will be when working through the items. All items should contain a concise description, if you imagine the reader has zero knowledge of the system would they understand what you are asking? Good briefs are user-focused. In agile, user stories are actually […]
Scaled Agile Framework®️ (SAFe®️) Agile Release Train (ART) CALMR (Culture, Automation, Lean flow, Measurement and Recovery) JIT (Just in Time) Verification and Validation (V&V) Lean Product Development (LPD) PDCA, Plan-Do-Check-Act PESTLE, sources of change (Political, Economic, Social, Technological, Legal, and Environmental) MoSCoW, used in prioritisation (Must-haves, Should-haves, Could-haves, and Will not have (or Wish-haves) VUCA, […]
Forming Positive and polite Some may feel anxious Eager to please, make an effort to get to know one another Storming Push against boundaries Conflict around working styles and personalities Frustrations around peoples differences in approach Some people question teams goals and avoid taking on tasks Some teams never get past the storming stage….. Norming […]