https://github.com/rominalodolo/scrummaster
Serum Master course via Udemy https://www.udemy.com/course/scrum-certification/
https://github.com/rominalodolo/scrummaster
agile-development agile-methodologies notes scrum
Last synced: 5 months ago
JSON representation
Serum Master course via Udemy https://www.udemy.com/course/scrum-certification/
- Host: GitHub
- URL: https://github.com/rominalodolo/scrummaster
- Owner: rominalodolo
- Created: 2024-02-26T07:21:34.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-03-04T12:41:48.000Z (over 2 years ago)
- Last Synced: 2025-03-01T13:42:03.085Z (over 1 year ago)
- Topics: agile-development, agile-methodologies, notes, scrum
- Homepage:
- Size: 104 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Overview of Scrum Agile project management+common questions+tips to pass PSM scrum org ONLINE Scrum Master Certification
>> Total 3 hours
>>
>> Notes captured here by Romina Lodolo on the 26th of Feb 2024.
## Section 1 : Introduction
Download this **PDF Scrum Guide** [2020-Scrum-Guide-US-highlighted.pdf](https://github.com/rominalodolo/ScrumMaster/files/14401159/2020-Scrum-Guide-US-highlighted.pdf)
**This course is Updated regularly + Scrum Guide Attribution and Use Scrum Guide Attribution and Use**
This course has the Scrum Guide Attached to it and uses screenshots of the Scrum Guide in order to draw your attention to the scrum rules. We have licensed the use of the Scrum Guide using the creative commons license below. For legal reasons, the following attribution and creative commons license have been added and relates to the scrum guide:
Author(s): Ken Schwaber and Jeff Sutherland
Link to source material: http://scrumguides.org/
License: http://creativecommons.org/licenses/by-sa/4.0/legalcode
No Changes: No changes have been made to the content of the scrum guide in this course, however parts of the Scrum Guide have been highlighted and excerpts of the scrum guide have been used within videos in this course.The licensor of the above license in no way endorses me or my use.
No Restrictions: I apply no legal terms or technological measures that legally restrict others from doing anything the license permits.
_This course is up to date_
"Hello there!
I just wanted to make sure you are absolutely certain that this course is using the November 2020 Scrum Guide. Any images used from the older scrum guide are purely for illustrative purposes :)
You will be given a link to the Open assessment (for practice) and Scrum Certification at the end of the course. There are also quiz questions along the way!"
Get the free Daily Team To-do list here to take your team to the next level!
### The Scrum To-do List
Want to deliver projects on time? Scrum To-Do Lists help you to do this. Understanding the fundamentals of scrum is a very simple thing to do. However putting it into practice in the world of deadlines, strong characters and the need for quick decisions can often make it a huge challenge to get the job done using the scrum rules. There are often situations where the rules are forgotten and put to one side, especially when they are most needed.
In my experience as a scrum master, team lead and software engineer I saw how easy it is for employees of a fast moving business to put the scrum rules to one side and destroy the very framework that would help make their daily lives easier. Observing how easy it is to forget the fundamental elements of scrum, I have put together this simple To-Do List that anyone can use on a daily basis. It covers:
To-Do List for the fundamental tasks of every scrum role
an overview and recap of each scrum meeting (time-box)
To-Do List for the preparation, carrying-out and goals of every scrum meeting
Using these To-Do List, you can be prepared and confident that you are carrying out the scrum practices on your daily job, boosting the productivity of your scrum team and increasing return on investment for the business. One section of the check list is below.
### The SCRUM MASTER To-Do List
o update list of impediments from daily scrum, emails and other contact
o follow up on impediments above
o order any team equipment
o write sprint report to stake holders (once a sprint)
o chase up any information holding up sprint backlog (eg. third party supplied artefacts)
o make sure burndown and task board are visible in team room
o arrange meetings and have chats to coach any new or needy team members, product owners or stakeholders
### The PRODUCT OWNER To-Do List
o update backlog daily with any changes
o prioritise backlog daily based on business value
o meet stakeholders when needed to coordinate and capture requirements
o liaise with team to clarify requirements and make trade offs communicate release plan to stakeholders
### The DEVELOPERS To-Do List
o update task board with time remaining on tasks
o report any impediments to scrum master
o communicate with product owner before attempting and after completing a story
o achieve daily targets
o maintain team communication
o keep solutions simple
o focus on ship-ability (e.g. using practices such as pair programming, code review, continuous refactoring)
### Check list
- [Daily Team Checklist](https://go.pashunconsulting.co.uk/daily-team-checklist-explainer32633470)
- Step 2 Prepare:
- Step 3: Meeting
- Summary: The team is well co-ordinated and planned for the day
- The whole development team is up to date with progress
- Any issues have been captured so that they can be removed as soon as possible
- The Facilitator has been informed if the issues are not simple for the team to resolve
## Section 2 : The world before agile and scrum
Learning objectives
1. What is wrong with traditional methods of project managemnt
2. What is the waterfall model and why it's less flexable than agile
3. What is agile and how is it different from scrum
Agile is not an alternative to Scrum but an umbrella term for a set of methodologies and frameworks that share a manifesto and a set of principles.
Scrum is one such framework.
Birth of agile:
Image of waterfall vs iterative method of the development process:
[XP, FDD, DSDM, and Crystal Methods of Agile Development](https://project-management.com/xp-fdd-dsdm-and-crystal-methods-of-agile-development/)
- XP
- Crystal
- DSDM
- FDD
The object mentor group agreed on set of principles and made [the manifesto for agile software developmemnt](https://agilemanifesto.org/)
[Waterfall model](https://www.youtube.com/watch?v=bNLcRdrSQAU)
- SDLC: linear, sequential approach to the software development lifecycle
- If the requirements change after the requirements phase, then this has a knock-on effect to the other phases, therefore, the launch date becomes more difficult to hit. On top of that, the bulk of the defects and issues are not usually found until the test phase. This often delays launch, since more time is needed to fix bugs. This situation usually leads to overtime, low morale, and a last minute scramble towards the end of the project.
## Section 3 : Introducing Scrum
1. What is [Scrum](https://www.techagilist.com/agile/scrum-theory-scrum-framework/)
Self Managing cross functional TEAMS
Scrum theory
* Iteratve
* Incremental
* Theories: Transparancy, Inspection, Adaptation
**Scrum skeleton**
**Self-Managing over Self-Organizing**
Scrum teams are self-managing, choosing who does the work, how, and what to work on.
**Lean Thinking**
As well as Empiricism, Scrum is founded on Lean Thinking. Lean thinking reduces waste and focuses on the essentials. as you will see Scrum removes waste (impediments) and prioritises value (essentials).
3. What the core theory of scrum is
Its a framework not a comeplete process
4. An overview of the Scrum practices
* Deliving often.
* Using evidence from the past to keep improving.
* Inspection shouldn't be too frequent that it gets in the way of doing actual work.
4 formal events for inspection and adaptation:
1. Sprint planning
2. Daily Scrum
3. Sprint Review
4. Sprint Retrospective
_Empiricism is about learning from the mistakes from the past_
[**Sprint**](https://www.atlassian.com/agile/scrum/sprints)
A sprint is an iteration of a calender month or less in which a product increment is delivered.
Setting sprint length should give enough opportinity to inspect and adapt.
**How to plan and execute scrum sprints**
5. Scrum Guide Gotchas
Find the full guide here: [2020-Scrum-Guide-US-highlighted.pdf](https://github.com/rominalodolo/ScrumMaster/files/14401159/2020-Scrum-Guide-US-highlighted.pdf)
## Section 4 : Scrum team accountabitlities
Scrum Team
1. Scrum master:
* Understanding the scrum rules,
* remove impepements and
* help team slef manage
* Go-to person
* facilitates meetings
* helps product owner to maximize ROI
* aids team in porductivity
2. Product owner
* creates product backlog and provides featutes needed
* makes decisions for ROI
* tradeoff to maximise product value
* priooritise requiremnets based on business value
3. The developers
* Self managing and collaborative
* Multi-skilled for the project, experts in their field
**Developers and Scrum Team Size**
> Development Team is now referred to as "developers"
>> The goal was to eliminate the concept of a separate team within a team that has led to “proxy” or "us and them” behavior between the PO and Dev Team. There is now just one Scrum Team focused on the same objective, with three different sets of accountabilities: PO, SM, and Developers.
> Scrum Team Size
>> The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people. In general, we have found that smaller teams communicate better and are more productive. If Scrum Teams become too large, they should consider reorganizing into multiple cohesive Scrum Teams, each focused on the same product.
Note: The size of the scrum team above is not prescribed. It is recommended.
**The Product Owner**
* Product Owner is responsible for maximising value of product & Developers
* What a Product Owner isn't responsible for
* What a Product Owner is accountable for
* Product Owner accountable for prouct backlog
* remind how YOU add value
* Prioritising
* using info from the teams to help make decisions
_For the Product Owner to succeed the entire organisation must respect their decisions_
**The Development Team**
* The developers consit of professionals who do the work of delivering a potenially releasable Increment of 'DONE' product at the end of each sprint
* DONE increment is key
* Scrum recognises no titles for the developers members other than developer, regardless of the work being performed by the other person; there are no exceptions to this rule.
[Sprint backlog info](https://medium.com/@KnowledgeHut/from-creation-to-execution-how-sprint-backlog-helps-scrum-teams-6b01ffaf1eb)
> [Open assesment](https://www.scrum.org/open-assessments/scrum-open):
>
> [Learning path for above assessment](https://www.scrum.org/pathway/scrum-master/)
>
**[Scrum Master](https://www.productplan.com/learn/scrum-master-responsibilities/)**
_Scrum master is a servent leadership - always serving the team. Serving the team by leading the team._
* Facilitating scrum events as required or needed.
* Removing any impediments
* Authority to coach and lead anyone in the organisation.
* Be the authority on scrum.
## Section 5 : Scrum events
1. Scrum events
Time box / Event
Ending and managing meetings on time.
Scrum masters role to organise and manage these meetings.
**Sprint planning meeting - 8 hours for 1 month sprint.**
Team plan the work for the next sprint
4 hours meeting for a 2 week sprint
3 topics - why(sprint goal), what, how.
Daily scrum:
1. What did I do yestrday that helped us meet the sprint goal?
2. What will I do today to help us meet the sprint goal?
3. Do I see any impediment that prevents me or us from meeting the Sprint goal?
Sprint review help after the sprint by the scrum mater. Sprint retrospective is held after the sprint review and before the next sprint. Each team member is asked what worked and what cuold be done better.
**Release Planning meeting**
Not officially a scrum event but often used in scrum.
Product backlog items prioritised for release.
Team agrees on what is feasible for release.
An indicator not a commitment.
The 5 Scrum events: The sprint, Sprint planning, Daily scrum, Sprint review, sprint retrospective.
Max length of a daily scrum = 15min. There is no minimum time.
All events are compulsory otherwise you are not doing a scrum.
_Prescribed events are used in Scrum to create regulatirt and to maximize the need for meetings not defined in scrum. All events are time-boxed events, such that every event has a maximum duration._
Very important to having a limit on time on projects and meetings.
If you're not doing all these events you're not doing SCRUM:
- Sprint planning
- Daily scrum
- Sprint review
- Sprint retrospective
>>_The heart of scrum is a sprint, a time-box of one month or less during which a "DOne", useable, and potentially releasable product Increment is created._
>>
>>_A new sprint starts immedietly after the conclusion of the previous Sprint._
>>
>>_Each Sprint may be considered a project with no more than a one-month horizon._
Canceling a sprint is done only by a Product owner.
Sprint planning:
- Sprint planning is a time boxed max of 8 hours per month
- For a 2 week sprint, a 4 hour meeting usually works.
- 4 hour meeting can have breaks but it's becuase there is that much to talk about when planning.
- Maybe could be reduced to 2 hours when you have more experience and know how to plan better.
Changes to Sprint planning rules:
Topics coved in Planning
* The Why : Sprint goal - Kick off the meeting
* The What : Actions, what needs to be done
* The How : How will it get done
_projected capacity of the developers during the sprint_
How much time do the developers have? Who is available for what. Time for lunch, for travel, restroom breaks, time for other time consuming tasks.
Time available - Factored Unavailable time = capacity
this builds buffer bto the plan
How to plan working days:
5 working days : 1 day for planning and include all other unavailable time. So only 4 days and maybe only 4 of those hours are productive.
10 working days : 9 capacity days etc.
_The Sprint goal is an objective that will be met within the Spint through the implementation of the Product Backlog._
5. Purpose of these
Remember: Three Sprint Planning Topics
Remember: Sprint Planning addresses the following topics:
### Topic One: Why is this Sprint valuable?
The Product Owner proposes how the product could increase its value and utility in the current Sprint. The whole Scrum Team then collaborates to define a Sprint Goal that communicates why the Sprint is valuable to stakeholders. The Sprint Goal must be finalized prior to the end of Sprint Planning
### Topic Two: What can be Done this Sprint?
Through discussion with the Product Owner, the Developers select items from the Product Backlog to include in the current Sprint. The Scrum Team may refine these items during this process, which increases understanding and confidence. Selecting how much can be completed within a Sprint may be challenging. However, the more the Developers know about their past performance, their upcoming capacity, and their Definition of Done, the more confident they will be in their Sprint forecasts.
### Topic Three: How will the chosen work get done?
For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done. This is often done by decomposing Product Backlog items into smaller work items of one day or less. How this is done is at the sole discretion of the Developers. No one else tells them how to turn Product Backlog items into Increments of value. 9 The Sprint Goal, the Product Backlog items selected for the Sprint, plus the plan for delivering them are together referred to as the Sprint Backlog. Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
6. What happens in each event
7. Scrum guide and exam prep
## Section 6 : Scrum Artifacts
## Section 7 : Scaling scrum
## Section 8 : Final words and certification
## Section 9 : Practical examples and case study
#### Daily Scrum Example
[Video Examples](https://www.youtube.com/@AgileTrainingVideos)
[Agile Simulation - Part 20 | The Daily Standup | Agile Videos](https://www.youtube.com/watch?v=q_R9wQY4G5I)
## Section 10 : FAQs
**Certificate**
&& [The Scrum To-Do List](http://pashunconsulting.co.uk/blog/scrum_todo_list_blog/?utm_source=udemy&utm_medium=scrumcertcourse)
**The Scrum To-do List**
## Section 11 : BONUS materials
Audiobook: Kicking off a Project - from "The Power of Scrum in thew real world" & Sprint Planning - from "The Power of Scrum in thew real world"
### How scrum works presentation
### The Scrum Mega Pack PDF
[72+Reasons+Why+Scrum+Works+-+Roiles+Excerpt.pdf](https://github.com/rominalodolo/ScrumMaster/files/14480202/72%2BReasons%2BWhy%2BScrum%2BWorks%2B-%2BRoiles%2BExcerpt.pdf)
### 3 Top Blog Posts
1. [Scrum Starter Kit](http://pashunconsulting.co.uk/blog/scrum_kit_blog/)
2. [Top 3 Books that changed my life](http://pashunconsulting.co.uk/blog/3-books-that-changed-my-life-top-agile-books/)
3. [Build Anything with Scrum](http://pashunconsulting.co.uk/blog/plan-and-build-anything-with-scrum/)
### Summeries:
#### BONUS
[Free Daily Team Checklist](https://go.pashunconsulting.co.uk/lm-mps-daily-team-checklist)