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.