The document describes an example scenario of a project team using agile practices to develop a new website with a shopping cart for a client. It outlines the key agile practices used: assembling a cross-functional team, working in short iterations to develop features, prioritizing a backlog of user stories, daily stand-ups to track progress, demonstrating work at the end of each iteration, and reflecting on lessons learned to improve. The team uses these practices to iteratively develop and deliver the website's sales page and shopping cart features to the client.

1. Agile Scenarios

2. Core Practices

3. Let’s look at a real-life scenario
You are working as the Project Lead for the JGH Company,
and they want to deliver a new website with a shopping
cart.
This could just as easily be a new:
• Shed design
• Car design or
• Other physical product
Agile Core Practices

4. First, you ensure you have the right team
• The Product Owner – representing the customer (or who
you are delivering the product to internally)
• Developers
• Designers
• Testers
You notice there is a separate team in charge of shopping carts, so you ask them to provide
you with one person for the duration of your project, bringing them into the project team.
This is the Whole Team Approach.
Agile Core Practices

5. Next, you write down the High Level Features they want.
• Meeting with the Product Owner you find they want a:
1. Website sales page
2. Shopping cart
• The Product owner decides or has input into which
feature they want to deliver first.
This is Rolling Wave Planning, Feature Driven
Development, Incremental Project lifecycle.
Agile Core Practices

6. Next, you break down the features into assignable tasks,
shown as stories.
• The Product Owner advises the website sales page would be
good to be delivered first.
• Meeting with the Product Owner and the “three amigos” –
Developers, Testers and Business Analysts, you break them
down into “Given, When, Then” scenarios of similar size.
• You place these tasks in the Product Backlog of work – a list.
This is Decomposition, Collaborative User Story Creation.
Agile Core Practices

7. Next, you decide how much you can work on in your next
iteration of work.
• You and the team decide on two week iterations to deliver a
feature.
• Because this is the first “sprint”, or iteration each team member
estimates how many stories they can complete – this will adjust
over the next iterations as we come to know our “velocity”.
• All together, the team assigns 18 cards
• You place these cards on your Kanban board
This is Release and Iteration (sprint) planning.
Agile Core Practices

8. The team meet each day.
• Each person advises what they did since yesterday, what they
will do today, and any blockers they need help with.
• It is your job to help facilitate the removal of those blockers.
E.g. a developer needs a certain logo design that is not within your team – you reach out
to the team in charge of that design and help get it to your developer.
• You move the cards along the Kanban board until they are
done.
This is the Daily Stand-up.
Agile Core Practices

9. At the end of the Iteration, the team actually completes
20 cards.
• So our “velocity” was slightly higher than we thought. We will
use this as the baseline for the next iteration.
• Now, we demonstrate the feature to the product owner and
other customers or stakeholders.
• They give feedback or accept the feature as it is.
This is Demonstrations and Reviews (Sprint Review).
Agile Core Practices

10. Now, we reflect and improve.
• Once we’ve demonstrated the feature at our Sprint Review,
now we reflect as a team with a Retrospective.
• We ask: What went well? What could we improve? What did I
learn? What still puzzles me?
We can adjust the amount of work we start with to 20 cards or items.
We also might want to bring in a logo designer to our “whole team”, as we
had to go externally for that.
This is Retrospectives.
Agile Core Practices

11. We groom and prioritise the product backlog again, plan
the next sprint and do it all again.
• We’ve delivered the Website sales page, so we work with the
Product Owner and decide on the next feature – the shopping
cart.
• We break it down to tasks, assign 20 of them and place them
into the Kanban board for this iteration.
Agile Core Practices