Tag Archives: customer

progress – the story so far

image

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.

customer delight

tea is served

Teatime has a very special meaning in Morocco and anytime is teatime.

Here a returning tea maid walks through the alleys in Marrakech, Morocco after serving a tray of mint teas.

Specially prepared in metal teapots and served with extra sugar, the tea takes time to get used to, but soon becomes part of the travellers daily refreshments.

Even the tea pouring is a customer event in itself. The pot is moved up and down above the cup to help cool the tea before drinking.

The agile manifesto, just like the tea ceremony, puts the customer in the centre.

This goes alongside product focussed teams, collaboration with stakeholders and a readiness for change.

The customer requirements are communicated via the product backlog in a sorting determined by the product owner.

The product owner is the single individual responsible for the backlog and must ensure all stakeholder requirements are considered and maintained in a prioritised manner.

This backlog is then estimated on a user story level in order to manage the number of backlog items that can be developed in a single iteration.

presenting your product

stripes and stones

A rare opportunity to take a camera into Antwerp’s main art gallery led to viewing the exhibition in a broader art and art lover context.

This made the visit even more inspiring by allowing me to practice my art in a place of artistry.

The product review, whether to a product owner, stakeholder or customer circle is one of the key events in any iteration.

It provides the opportunity for the team to align on vision and release targets before looking at the current iteration. This is then done by engaging the stakeholders in an interactive review with a focus on the finished product increment.

This increment is reviewed against an agreed definition of done, to ensure the appropriate quality expectations are reached. The product increment should have been reviewed prior to the review meeting so that an approval by the product owner during the meeting can be assured.

Features that have not been completed in the sprint should not be presented in the review, although a customer will expect some indication of the progress made at that point in time.

Market information is provided by the market facing members of the team to ensure validity of the remaining backlog items. In some cases this can lead to an adjustment and inclusion of some product backlog items or their actual ordering.

Output is an approved product increment which works with all previous product increment accumulations. The product owner can but does not have to release this increment if it does not make sense to do so.