PMGT5871 Chap.11 Agile Values and the Scrum Framework
Agile Values and the Scrum Framework
Week 9 begins the Agile half of the unit. This chapter explains Agile as iterative delivery in small, consumable increments, reads the four Agile values with their qualifier and highlights the principles most often tested.
It contrasts the waterfall sequence with incremental delivery shaped by customer feedback, then sets out the Scrum framework: team size, the product owner, Scrum master and development team, the five Scrum events with their inputs and outputs, and the product vision.
From this week the unit's assessment shifts from the final exam, which covers Weeks 1 to 8, to the Agile deliverables: Group Assignment 2, an Agile project plan built in Jira, and the individual reflection on Agile planning.
The Week 9 tutorial uses the second case study, a start-up dating platform, and asks groups to set their Scrum team, write a product vision and list the platform's functions, which become the raw material for the backlog in Chapter 12.
What this chapter covers
- 01
What Agile delivery means
- 02
The four Agile values and their qualifier
- 03
Agile principles
- 04
Waterfall compared with iterative delivery
- 05
Scrum team size and roles
- 06
Discovery, sprint planning, daily scrum, sprint review and retrospective
- 07
The product vision
Worked example · free
Setting up a Scrum team and product vision
- 1Product owner: the student-services manager, who represents users and owns the backlog.
- 1Scrum master: a delivery lead who facilitates and removes obstacles.
- 1Development team: six generalist-specialists with each skill backed up.
- 1Vision: help any student book a qualified peer tutor quickly so small gaps are fixed early.
Key terms
- Scrum master
- The servant leader who facilitates team interactions, coaches, removes obstacles and enforces Scrum practice.
- Product owner
- The role that represents stakeholders, writes requirements as user stories and manages the prioritised backlog.
- Sprint review
- A showcase at the end of a sprint where working product components are shown to clients for feedback.
- Retrospective
- A meeting after one or two sprints in which the whole team reviews how it works and agrees improvements.
Agile Values and the Scrum Framework FAQ
Does Agile reject documentation and planning?
No. The four values rank individuals and interactions, working product, customer collaboration and responding to change above processes and tools, documentation, contract negotiation and following a plan. The slide is explicit that the lower-ranked side keeps its worth, so documentation and plans still exist in Agile projects.
How big is a Scrum team?
The Week 9 slides give five to nine people. A large project is divided into several streams, each with a team of the same size, rather than one very large team.
What happens in the daily scrum?
Every team member answers three questions: what they did yesterday, what they will do today, and whether any issues or blockers stop their work. The outputs are actions to assign or adjust work and to resolve blockers.
What does the product owner do in Scrum?
The product owner represents stakeholders and makes sure the team delivers value, writes business requirements as user stories with input from the team, manages the prioritised product backlog and communicates product functionality clearly, which is why the role is called the voice of the customer.
What is the difference between waterfall and Agile delivery?
Waterfall moves through requirements, design, development, testing and deployment once and delivers one final outcome. Agile delivers preliminary and intermediate outcomes in short iterations, with customer feedback after each one shaping the next increment.
What is a product vision?
It states why the product is being built, what its creators intend and what it should change for customers and users. It pictures a future state, names the problems the product will solve and sums up the value proposition, which later guides the product owner's ranking of stories.
Exam move
Learn the four values as pairs and say each one with its qualifier, because many wrong options claim that Agile abandons the right-hand item. Make a table of the five Scrum events with timing, participants, input and output, and test yourself by covering one column. For the roles, write a short scenario in which each role makes one decision that only it can make.
Then compare the waterfall and incremental models by drawing both and marking where the customer sees the product. This prepares you for the Jira assignment as well as the reflection on Agile planning. For the reflection assignment, keep notes after each Agile tutorial on what the Scrum roles and events changed in your group's way of working; specific observations are far easier to reflect on than general impressions.
Working through Agile Values and the Scrum Framework in PMGT5871? Sia is AskSia’s AI Project Management tutor — ask any PMGT5871 Agile Values and the Scrum Framework question and get a clear, step-by-step explanation grounded in how PMGT5871 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.