Welcome to the course on The Scrum Development Process. This is the third course of a series of eight that will form the Agile Project Management – The PMI-ACP (Agile Certified Practitioner) Certification Program.Who is your instructor?
An overview of the Scrum development process.
Scrum is one of the most popular agile methodologies to date, with tools and techniques applicable to more than just software development projects.
This course will assist prospective Scrum masters, product owners, and team members with the understanding of core Scrum practices. This includes an outline of the roles and responsibilities of members of the Scrum team, the importance of good communication, and the role of project stakeholders.
The course divides the Scrum development process into three major phases: pre-game, game, and post-game. It describes the activities performed in each phase, but particularly examines the activities and tools of the game phase.
Scrum basics covered include the use of product and sprint backlogs, the use of iterative development in the form of sprints, performing daily stand-up meetings, the use of sprint reviews and retrospectives, and using Scrum task boards and burn-down charts for monitoring and reporting project progress.
Who is your instructor?
My name is Sorin, and I will be your instructor. I am a trainer and project manager with more than 10 years of experience. Before Udemy, I trained hundreds of people in a classroom environment – civil servants, managers, project workers, aid workers and many more. And I managed projects in the fields of justice, corrections, regional development and human resources development.
How will you benefit?
This course is intended for project managers, program managers, or anyone who wants to efficiently participate in agile projects. It is aligned with the Agile Certified Practitioner exam objectives developed by the Project Management Institute® and Certified ScrumMaster learning objectives.
Training videos, examples, exercices and quizzes will help you learn all about the Scrum development process. And, if you take your time to go through all the learning materials this will entitle you to claim 5 PDU’s for the PMI certification exams and to maintain your PMI certification.
So, thank you for considering this course! Now, go ahead, and hit that “Take This Course” button. And, see you on the inside.
Managing a Scrum Project
-
1Program Overview
This video will help you understand better the content of the other courses that will form this Agile Project Management - The PMI-ACP (Agile Certified Practitioner) Certification Program.
-
2Course Overview
There are two main parts: one is called Managing a scrum project and the other The Scrum Process in Action.
-
3Course Guidelines
You might know this. I’m adding it to any course in the introductory section. But, just in case some suggestions to improve your learning.
-
4Course Overview
There are two main parts: one is called Managing a scrum project and the other The Scrum Process in Action.
The Scrum Process in Action
-
5The Agile Manifesto and Agile Principles
The Agile Manifesto and Agile Principles
-
6Defining Scrum
The term "scrum" originates from the rugby formation, in which a team's players work together to gain possession of the ball. The agile methodology of Scrum borrows this term to describe a framework of project management processes and techniques. Scrum enables project teams to develop complex products quickly and efficiently, to adapt to change, and to regularly deliver value to customers in the form of working products.
-
7The scrum approach
The scrum approach
-
8The product owner
The product owner is usually a customer representative, whose main focus is to represent the interests of the customer throughout the development process. The product owner measures how well a project performs in terms of return on investment, or ROI.
-
9The Scrum Master
In a Scrum team, the Scrum Master is the expert on all Scrum-related issues and ensures that everyone works according to Scrum principles and practices. He or she should also shield the development team from external processes and control, so they can fully concentrate on development. The Scrum Master may be a member of the development team.
-
10The development team
A Scrum team usually consists of five to nine individuals who share the responsibility for developing a product and delivering it to the product owner at the end of each sprint. The optimal team is self- organizing and cross-functional.
-
11Agile project team, scrum team, and development team
Agile project team, scrum team, and development team
-
12The Scrum team in practice
You're working as a Scrum Master on a project that involves developing tracking software for a transport company.
-
13Communicating with stakeholders
In the Scrum approach, effective communication is vital for ensuring that a Scrum team understands customer requirements, and that development team members can work together efficiently to solve complex problems.
-
14Scrum meetings
The role of Scrum meetings is to ensure communication flows smoothly between the different stakeholders and team members. There are five types of Scrum meetings – the sprint planning meeting, the daily standup meeting, the Scrum of Scrums, the sprint review meeting, and the sprint retrospective
-
15Sprints are recurring processes
Sprints are recurring processes.
-
16The pre-game phase
The core of Scrum, originally referred to as the "game" by its creators, describes how to prepare and run Sprints. While not officially described as such in the Scrum guide, the phases of a Scrum project cycle could be considered and are sometimes described as pre-game, game, and post-game.
-
17The game phase
The game phase refers to the sprint, or development, phase. This is when the development team plans each sprint and proceeds to create functioning product deliverables, also called potentially shippable product increments.
-
18The post-game phase
The work needed after a sprint or series of sprints to release the product, is sometimes referred to as the post-game phase.
-
19A scrum task board on a wall or whiteboard
A scrum task board on a wall or whiteboard
-
20Managing a Scrum Project
Understand Scrum team roles, guidelines for effective stakeholder communication, project activities and phases in the Scrum development process
The Scrum Development Process
-
21Pre-game planning
At the start of a new Scrum project, some initial planning and design must take place in order to define a project goal and product backlog for the project.
-
22Developing a high-level design
Once the product owner has compiled project requirements, the development team reviews the backlog and creates a high-level design for the product to be developed.
-
23Sprint planning
The game phase is where the core Scrum practices exist and where the bulk of the work is done. The development team plans each sprint, meets regularly, and creates functioning deliverables. And at the end of each sprint, it delivers the results to the customer, or a customer representative, for review. The process is iterative, with a product developed incrementally over multiple sprints.
-
24Sample sprint backlog
Sample sprint backlog
-
25Daily standup meetings
During the course of a sprint, the members of a Scrum team meet to discuss task progress and any issues that are preventing tasks from being completed.
-
26Unit tests and sprint reviews
Ongoing testing and the adaptation based on test results is a key principle of most agile methodologies, including Scrum. During the game phase of the Scrum development process, this principle is implemented in two ways – through unit testing and sprint reviews.
-
27Sprint retrospectives and closure
After each sprint review meeting, the Scrum Master conducts a sprint retrospective with the development team to discuss how the sprint went and how it could have been improved. This helps the team formulate best practices it can apply during the next sprint, in keeping with the agile principle of continuous improvement.
-
28Burndown charts
At any point in a project, it's important to know how the project is progressing. That way, team members can make necessary adjustments – and other stakeholders can verify that everything is on track. Scrum teams use various highly visual tools to track their progress during each sprint. These include burndown charts and various progress charts.
-
29A burndown chart
A burndown chart
-
30Progress charts
As well as burndown charts, a Scrum team may use various progress charts - to track its progress in completing the tasks in each sprint
Both burndown charts and progress charts let you compare actual and estimated values, and both provide a quick, highly visual way to track progress.
-
31The Scrum Task Board
When practicing Scrum we can make the sprint backlog visible by putting it on a Scrum task board. Team members update the task board continuously throughout the sprint; if someone thinks of a new task (“Test the snark code on Windows 8.1”), she writes a new card and puts it on the wall.
-
32Using tracking metrics
As well as charts, you can use various metrics to track and report on the progress of a Scrum project. All visual ways to track progress, within the sprint or on project level, are called progress monitors.
Metrics that you can use to track the progress of a project include velocity, standards violation, business value delivered, number of defects per iteration, number of stories, level of automation, and number of tests.
-
33The Scrum Process in Action
At the start of a new Scrum project, some initial planning and design must take place in order to define a project goal and product backlog for the project.