Tag Archives: sprint

progress – the story so far


An infographic capturing the progress to date of my own product – this “photographic image inspired agile story telling blog”.

The tag cloud app on the iPad scans the page and creates an image of words.

Another infographic in a few months will show as a snapshot in time what progress has been made with this personal product of mine.

Similarly, in any Sprint operating within a Scrum development framework, it is vital to understand the progress being made with the product development against the goal for the iteration. Progress is assessed on a daily basis, against the Sprint Goal which is agreed between the Product Owner and Development Team during Sprint Planning at the start of each iteration.

As the iteration progresses, the plan is adjusted on a daily basis to ensure the team as a whole is aligned and understands what is needed to meet the Sprint Goal at all times. The plan is inspected on a daily basis by reviewing the Sprint Backlog to assess the progress towards the Sprint Goal. This continues throughout the iteration with the Development Team working closely with the Product Owner to adapt the Sprint Backlog to continually  meet the Sprint Goal.

The actual product or software Increment produced in any Sprint is reviewed at the end of iteration in the Sprint Review to understand what has actually been completed in the Sprint. Completed means that all work needed to meet the expectations of the Product Owner are “done” as specified in the Definition of Done including the acceptance criteria describing the functional aspects for each Product Backlog Item.

The Increment is inspected in the Sprint Review which provides an opportunity to gather feedback from the broader internal or external stakeholder community. Adaptation is then made to adjust to the overall Product Backlog which documents all the ambitions for the product in the future. The adjusted Product Backlog is adapted based on changed market or customer input, or simply to keep the product on track with product release plans or overall product vision.

just enough is good enough

Images that caught my attention were plenty on the trip to Japan.

Even the most simple things like these threads on a Yokohama market stall were picked up in the lens.

It was a delight to have the camera at hand at all times and built more than enough photo stock for my 365 day photo project.

More from the land of the rising sun on Flickr

Planning is just as important in an agile environment, only the attention to detail is different.

A plan is made of differing horizons – task, sprint, release levels.

Across these horizons the level of detail decreases from task to release meaning the right level of attention is paid at the right time.

Long term plans simply provide false security, while agile planning aims for the right level of detail at the right time.

Quite likely the total planning activity over the lifetime of a project is greater for an agile project, but the focus is on plan-develop-plan-develop rather than a single planning and single development phase.