├── psm1-badge.pdf ├── img ├── bookmark.png ├── burndown-chart.png ├── overview-diagram.png ├── see-all-questions.png └── bookmarked-questions.png ├── how-to-face.md └── README.md /psm1-badge.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ambaena/scrum-psm1-cheatsheet/HEAD/psm1-badge.pdf -------------------------------------------------------------------------------- /img/bookmark.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ambaena/scrum-psm1-cheatsheet/HEAD/img/bookmark.png -------------------------------------------------------------------------------- /img/burndown-chart.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ambaena/scrum-psm1-cheatsheet/HEAD/img/burndown-chart.png -------------------------------------------------------------------------------- /img/overview-diagram.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ambaena/scrum-psm1-cheatsheet/HEAD/img/overview-diagram.png -------------------------------------------------------------------------------- /img/see-all-questions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ambaena/scrum-psm1-cheatsheet/HEAD/img/see-all-questions.png -------------------------------------------------------------------------------- /img/bookmarked-questions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ambaena/scrum-psm1-cheatsheet/HEAD/img/bookmarked-questions.png -------------------------------------------------------------------------------- /how-to-face.md: -------------------------------------------------------------------------------- 1 | # 📝 Professional Scrum Master 1 (PSM I) **ambaena empirical guide** to face the assessment. 2 | 3 | **`Disclaimer:`** First to clarify that this is based on my **own experience** dealing with **Scrum PSM-1 assessment**. This is not the absolute truth. 4 | 5 | ## **Where** i am ready?. 6 | 7 | - ❌ Reading or understanding the **Scrum Guide is not enough**. 8 | - ✅ **Consistently pass** the preparation exams you are using. I mean doing **some in a row with score close to 100%**. 9 | - ✅ **Be able to perform** at least **3-5 Scrum Opem Assessments** in a row with **100%**. In less than **6-8 mins each** of them. 10 | 11 | ## **How** to face the assessment. 12 | 13 | 14 | - **Before the assessment**: 15 | - 🤓 **Read** the official [SCRUM Guide](https://scrumguides.org/scrum-guide.html) at least a couple of times more **before facing the assessment**. 16 | - 🤓 **Read** the cheatsheet (preferably your own cheatsheet) as well. 17 | - 🔍 **Review questions** that you have **failed most recently in your practice assessments** (public exams on the internet, **Scrum Open Assessments**). 18 | - 🏋🏻‍♂️ Do at least **one Open Assessment** to **warm up/prepare** you and your mind to what is to come. 19 |
20 |
21 | 22 | - **During assessment**: 23 | - 💻 Use a **computer/laptop exclusively to take the exam.** Only to answer the questions. Scrum does not allow you to copy the statement, so you will not be able to take advantage of this to look up a question in Google. 24 | - 📚 **Prepare another computer for the support material**, remember that the assessment **is open book**. You can use any resource you want to solve it. I recommend: 25 | - Have the [Scrum Guide](https://scrumguides.org/scrum-guide.html) open. Ready in case you need it. *(`control + F`)* 26 | - Have your favorite cheatsheet open. *(`control + F`)* 27 | - In case you are not a native English speaker, have a **dictionary open in your browser**. 28 | - A window with **Google to search** in case of doubt the **statement** of the question in Google. For 90% of them you will find it on some website. Although the **answers will not necessarily be correct**, use what you find to **support your own thinking**. In case you have no idea, better to answer what you find on Google than nothing :) 29 | - 🏃🏻‍♂️ In the **first loop do not waste too much time on any question**, use the **marker 🏷 to mark all the questions that you have answered with doubt**. 30 | 31 | ![](/img/bookmark.png) 32 | - 🕵🏻‍♂️ Spend the **remaining time to review** marked questions or even **Google it**. 33 | 34 | ![](/img/see-all-questions.png) 35 | ![](/img/bookmarked-questions.png) 36 | 37 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # 📚 Professional Scrum Master 1 (PSM I) cheatsheet. 2 | 3 | ## **TOC** 4 | 5 | * [**What is SCRUM?**](#--what-is-scrum---) 6 | * [**Big Picture**](#--big-picture--) 7 | * [**Scrum Guide**](#--scrum-guide--) 8 | * [**Agile Manifesto**](#--agile-manifesto--) 9 | + [Project](#project) 10 | + [Product](#product) 11 | + [People](#people) 12 | + [Process](#process) 13 | * [**SCRUM Theory**](#--scrum-theory--) 14 | * [**SCRUM Values**](#--scrum-values--) 15 | * [**SCRUM Team**](#--scrum-team--) 16 | + [Product Owner.](#product-owner) 17 | + [Developers.](#developers) 18 | + [Scrum Master.](#scrum-master) 19 | * [**SCRUM Artifacts**](#--scrum-artifacts--) 20 | + [Product Backlog](#product-backlog) 21 | + [Sprint Backlog](#sprint-backlog) 22 | + [Incremental](#incremental) 23 | * [**SCRUM Events**](#--scrum-events--) 24 | + [Sprint Planning:](#sprint-planning-) 25 | + [Sprint](#sprint) 26 | + [Daily Scrum](#daily-scrum) 27 | + [Sprint Review](#sprint-review) 28 | + [Sprint Retrospective](#sprint-retrospective) 29 | * [**Definitions**](#terms) 30 | * [**HOW TO FACE THE PSM1 ASSESSMENT**](#how-to-face-the-assessment) 31 | 32 | ## **What is SCRUM?** 33 | 34 | Scrum is a lightweight framework that helps people, teams and organizations generate value through 35 | adaptive solutions for complex problems. 36 | 37 | ## **Big Picture** 38 | 39 | ![alt text](img/overview-diagram.png "SCRUM Big Picture") 40 | 41 | - **`Artifacts`**: *Product Backlog, Sprint Backlog and Incremental.* 42 | - **`Events`**: ***Sprint**, Sprint planning, Daily, Sprint review and Sprint retrospective* 43 | - **`Accountabilities`**: *Product Owner, Developers and SCRUM Master* 44 | 45 |
46 | 47 | ## **Scrum Guide** 48 | 49 | Scrum Guide as the official standard about Scrum!. 50 | 51 | 52 | 53 | It is recommended reading, it is a very condensed document with all the necessary information to understand SCRUM. 54 | 55 | [SCRUM Guide (English)](https://scrumguides.org/scrum-guide.html) 56 | 57 |
58 | 59 | ## **Agile Manifesto** 60 | 61 | Scrum is strongly **based** on `Agile Manifesto`. This is **not mandatory** to pass **PSM1** assessment, but is **good to know**. 62 | 63 | We can divide 12 principles of Agile Manifesto in four differents categories: 64 | 65 | - Project 66 | - Product 67 | - People 68 | - Proccess 69 | 70 | 71 | ### Project 72 | 73 | - *Our highest priority is to satisfy the customer throught early and continuous delivery of **valuable software*** 74 | - ***Welcome changing requirements** even late in development. Agile processes harness change for the customer`s ompetitive advantage* 75 | - ***Deliver** working software **frequently**, from a couple of weeks to a couple of months, with a preference to the shorter timescale* 76 | - *Agile processes promote **sustainable development**. The sponsors, developers, and users should be able to maintain a constant pace indefinitely* 77 | - ***Working software** is the primary measure of **progress*** 78 | 79 | ### Product 80 | 81 | - ***Simplicity** is essential* 82 | - *Continuous attention to **technical excellence** and good design enchances agility* 83 | 84 | ### People 85 | 86 | - *The most efficient and effective method of conveying information to and within a development team is **face-to-face conversation*** 87 | - ***Bussines** and **developers** must work **together** daily throughout the project* 88 | - *The best archictectures, requirements, and designs emerge from **self-organizing teams*** 89 | - *Build projects around **motivated** individuals. **Give** them the environment and **support** they need, and **trust** them to get the job done.* 90 | 91 | 92 | ### Process 93 | 94 | - *At **regular intervals**, the team **reflect** on how to become more effective, then tunes and adjusts its behaviour accordingly* 95 | 96 |
97 | 98 | ## **SCRUM Theory** 99 | 100 | > Scrum is founded on **empiricism** and lean thinking. Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Lean thinking reduces waste and focuses on the essentials. 101 | 102 | - `Transparency`: The emergent process and work must be visible to those performing the work as well as those receiving the work. 103 | - `Inspection`: The Scrum artifacts and the progress toward agreed goals must be inspected frequently and diligently to detect potentially undesirable variances or problems. To help with inspection, Scrum provides cadence in the form of its five events. 104 | - `Adaptation`: A Scrum Team is expected to adapt the moment it learns anything new through inspection. 105 | 106 | > **Transparency** enables inspection > **Inspection** enables adaptation > **Adaptation** 107 | 108 |
109 | 110 | ## **SCRUM Values** 111 | 112 | > Successful use of Scrum depends on people becoming more proficient in living five values. 113 | 114 | - `Commitment`. 115 | - `Courage`. 116 | - `Openness`. 117 | - `Focus`. 118 | - `Respect`. 119 | 120 |
121 | 122 | 123 | ## **SCRUM Team** 124 | 125 | **`Composed by:`** 126 | - **Product Owner** (PO) [x1] 127 | - **Scrum Master** (SM) [x1] 128 | - **Developers** (Devs) [< x10] 129 | 130 | 131 | > If Scrum Team come large, they should consider reorganizing into multiple cohesive teams, each focused in same Product. **They should share same Product Goal, Product Owner and Product Backlog** 132 | 133 | ### Product Owner. 134 | - Maximizes the **value** delivery chain. 135 | - Manages the **Product Backlog**. 136 | - The Product Owner represents the interests of the business or community product stakeholders through the content and order of the Product Backlog. 137 | - Customer interaction. 138 | - **Main** responsible for engaging the stakeholders, but not unique. All Scrum team is responsible. 139 | - Progress inspection. 140 | - Product Owner must have **authority**. 141 | 142 | ### Developers. 143 | - They are responsible for transforming the idea reflected in the **Product Backlog** into **Incrementals**. 144 | - **Self-Managed** and **Cross-Functional**. 145 | - Allowed to update **Product Backlog**, but the PO remains accountable. 146 | - Estimate the **size** of the **Product Backlog**. 147 | 148 | ### Scrum Master. 149 | - Is responsible to make **Scrum** run smoothly. 150 | - **Accountable** for establishing Scrum. 151 | - Cause the removal of **impediments**. 152 | - **Coaching.** 153 | - **Meeting facilitation.** 154 | - Actions may take in starting up Scrum implementation: 155 | - Ask the developers to introduce themselves to each others and tell about their skills and background. 156 | - Ask the PO to explain the product, its bussines need, history, goals... 157 | - Ask the developers to discuss and identify the way they are going to develop the product. 158 | - **Facilate stakeholders collaboration** as requested or needed. 159 | 160 |
161 | 162 | **`Staled Scrum:`** 163 | - Multiple Scrum teams working on **one product.** 164 | - Only **one** Product Owner per Product Goal, so per Product Backlog. 165 | - **One integrated Increment**, so unique Increment. 166 | - Don't need to be synchronized. 167 | - Definition of Done for teams, but every team can have own DOD. Team DOD is a minimum that every team must follow. 168 | 169 |
170 | 171 | ## **SCRUM Artifacts** 172 | 173 | Each artifact contains a commitment: 174 | 175 | | Artifact | Commitment | 176 | |-----------------|-------------------| 177 | |`Product Backlog`| Product Goal | 178 | |`Sprint Backlog` | Sprint Goal | 179 | |`Incremental` | Definition Of Done| 180 |
181 | 182 | ### Product Backlog 183 | 184 | - Represent **work-to-do** 185 | - It is **never complete.** 186 | - Commitment: **Product Goal** 187 | - Is posible to have multiple product goal's, but the Scrum team will **focus** on one product goal at a time. 188 | - The Product Backlog is an **emergent**, ordered list of what is needed to improve the product. 189 | - It list all features, functions, requirements, enhancements and fixes that constitute the changes to be made to the product in future release. 190 | - It is the **single source of work** undertaken by the Scrum Team. 191 | - A **Product** has a **single** Product Backlog, no exceptions here. 192 | - Epics -> User Stories. 193 | - Product Backlog **Refinement** required as time is **needed**. 194 | - The **Product Owner** orders it considering whatever he/she judges as appropiate. Order by 4 factors: 195 | - Size 196 | - Risk 197 | - Value 198 | - Dependences 199 | 200 | **`Monitoring progress`** 201 | 202 | Three diferents ways proposed by Scrum Guide to control/monitoring the progress: 203 | 204 | - `Burn-down chart`: **top-to-bot** with remaining work to do and estimated remaining work to do (like story points) by unit of time (like sprints or days) 205 | 206 | ![Burn-down chart](img/burndown-chart.png) 207 | 208 | - `Burn-up chart:` **bot-to-top**. Same that burndown chart but with the amount of work done and amount of work to do. 209 | 210 | - `Cummulative flow chart.` 211 | 212 |
213 | 214 | ### Sprint Backlog 215 | 216 | - Represent **work-to-do** 217 | 218 | >The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how). 219 | 220 | - By and for the developers. **Only devs can change** the Sprint Backlog. 221 | 222 | - **Sprint Goal** is fixed, but **Sprint Backlog** could have changes without change the Sprint Goal. 223 | 224 | ### Incremental 225 | 226 | - Represent **value** 227 | - Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable. 228 | - Work cannot be considered part of an Increment unless it meets the Definition of Done. 229 | - Definitions Of Done (DOD): 230 | > A **formal description** of the state of the increment when it meets the **quality** measures required for the product. 231 | - Each Increment has **only one** DOD. 232 | - The organization defined DOD, if the organization does not have one, the scrum team must define one appropiated DOD. 233 | - You **dont need** to release Increment at the end of every sprint. 234 | - The Sprint **is not a gate**, release might be performed during a sprint. 235 | 236 | 237 |
238 | 239 | ## **SCRUM Events** 240 | 241 | - **`Timmings:`** 242 | 243 | - `Sprint`: No more than **1 month**. 244 | - `Sprint planning`: Maximun of **8 hours** for a one-month Sprint. 245 | - `Daily`: **15 min**. 246 | - `Sprint Review`: Maximun of **4 hours** for a for a one-month Sprint. 247 | - `Sprint Retrospective`: Maximun of **3 hours** for a for a one-month Sprint. 248 | 249 | - Events are a formal opportunity to inspect and adapt something. 250 | 251 | ### Sprint Planning: 252 | 253 | - `Who`: 254 | - Scrum Team. 255 | - Invited Stakeholders if needed. 256 | - `Topics:` 257 | - **Why is this Sprint valuable?** *Sprint Goal* 258 | - **What can be done this sprint?** *Sprint Backlog* 259 | - **Measure:** Past performance, their upcoming capacity, and their Definition of Done 260 | - **How will the chosen work get done?** *Increment* 261 | 262 | ### Sprint 263 | 264 | - ***The Heart of Scrum*** 265 | - Defined before **Sprint Planning** and cannot be modified later (except when the sprint is cancelled). 266 | - **Must have** fixed durations. 267 | - **During sprint**: 268 | - No changes are made that would endanger the Sprint Goal. 269 | - **Quality** goals **no decrease** 270 | - The Product Backlog is refined if needed. 271 | - **Only** the **Product Owner** has the autority to cancel de Sprint. 272 | - `Invalid Sprints`: 273 | - Hardening, stabilization sprints.. 274 | - Sprint 0 275 | - Release Sprint 276 | - Design Sprint 277 | 278 | ### Daily Scrum 279 | 280 | - Where developers talk about their **progress** toward the **sprint goal** and to **adapt** the **Sprint Backlog** as needed. 281 | - The Scrum Master only needs to ensure that the meeting takes place. 282 | - The **Product Owner** neither participate in the meeting. 283 | - If **SM** or **PO** participate, they do as **developers**. 284 | - No time to discuss the solution to a problem. Not technical meeting. 285 | - Topics: 286 | 1. Impediments 287 | 2. What work i did yesterday to achieve goal? 288 | 3. What work i am going to do today to achieve goal? 289 | 290 | ### Sprint Review 291 | 292 | - The **Goal** is **inspect** the increment or any other outcome of the Sprint. 293 | - **Adapt** Product Backlog if needed. 294 | - **Undone work** is **NOT** presented during Sprint Review. 295 | - Sprint Review is based on **transparency** and **colaboration**. 296 | 297 | ### Sprint Retrospective 298 | 299 | - Entire **Scrum Team** participate. 300 | - The purpose of the Sprint Retrospective is to plan ways to **increase quality** and **effectiveness**. 301 | - The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. 302 | - After Sprint Review, and **conclude** the **Sprint**. 303 | - What went/didnt went well during the sprint? 304 | - How we can improve? 305 | - Discuss **DOD**. 306 | - Discuss the **composition** of the team. 307 | 308 | 309 | ## **Terms** 310 | 311 | - **`SCRUM`**: 312 | - *A mechanism to optimize the value delivery system.* 313 | - *A mechanism to guide changes.* 314 | - **`Effectiveness`**: 315 | - *Delivering the right product* 316 | - **`Efificiency`**: 317 | - *Making the team, the people, work as best way* 318 | - **`IKIWISI`**: 319 | - *I Know It When I See It* 320 | - **`YAGNI`**: 321 | - *You Ain`t Gonna Need It* 322 | - **`Agility or be agile`**: 323 | - *Agility means responding to change.* 324 | - **`Definition Of Ready`**: 325 | - *Set of criteria that defines when a Product Backog item is ready to be execute.* 326 | - **`Bottom-up intelligence`**: 327 | - ** 328 | - **`Product`**: 329 | - *A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users or customers. A product could be a service, a physical product, or something more abstract.* 330 | - **`Product Vision:`** 331 | - *What drives all the effort to build a product, describint the ultimate reason for creating it* 332 | - **`Product Strategy:`** 333 | - *Is where we define how to the vision will be realized* 334 | - **`Epics:`** 335 | - *Short reminders of stuff that the product will have.* 336 | - *Briefly describe the product features.* 337 | - **`User Stories:`** 338 | - *To describe small Product Backlog items.* 339 | - **`Story Point:`** 340 | - *Story points are a unit of measure for expressing an estimate of the overall effort that will be required to fully implement a product backlog item or any other piece of work* 341 | - **`Planning Poker:`** 342 | - *Is a consensus-based, gamified technique for estimating* 343 | - **`Upcomming Capacity:`** 344 | - *How many hours available the Developers have for this Sprint* 345 | - **`WIP:`** 346 | - *Work In Progress.* 347 | - **`Cone of Uncertainty:`** 348 | - *Describes the reduction of the uncertainty about scope after each iteration.* 349 | - **`Technical debt`:** 350 | - *Consequences of poor software development practices.* 351 | 352 |
353 | 354 | ## **HOW TO FACE THE ASSESSMENT**: 355 | 356 | In the following `.md` *([how-to-face.md](how-to-face.md))* we will discuss it. --------------------------------------------------------------------------------