Get Started. It's Free
or sign up with your email address
Scrum study guide mind map by Mind Map: Scrum study guide mind map

1. Scrum Master Manifesto


1.2. First created at the Scrum Alliance Global Gathering London,

1.2.1. 11-13 October 2011

1.3. 12 ScrumMaster Pocket Principles

1.3.1. 1. Dedicated Delivery Improver

1.3.2. 2. Foster Continuous Improvement

1.3.3. 3. Help Continuous Improvement

1.3.4. 4. Empower Coach Deliver

1.3.5. 5. Nurtures The Team

1.3.6. 6. Transparent Team Helper

1.3.7. 7. Commitment To Excellence

1.3.8. 8. Empathetic Evangelistic Guide

1.3.9. 9. Resistant Persistent Dedicated

1.3.10. 10. Help the Team

1.3.11. 11. Awareness Then Improvement

1.3.12. 12. Agile Driving Force

1.4. Top 10 things a ScrumMaster usually forgets to focus on (but is not SOLELY responsible for) ...

1.4.1. 1. Redefining career paths and goals to be more scrum focussed

1.4.2. 2. Missing Product Backlog items

1.4.3. 3. Team issues aren't being discussed because they are too uncomfortable

1.4.4. 4. Appropriate balance between end-to-end system test and unit tests

1.4.5. 5. Playing back the team's progress against the proposed release plan

1.4.6. 6. All tests roll up into the continuous integration results

1.4.7. 7. Team members realise the benefits of refactoring

1.4.8. 8. Code is regularly peer reviewed

1.4.9. 9. Pair programming is being utilised

1.4.10. 10. Definition of done is being expanded

2. Roles (3)

2.1. Scrum Team

2.1.1. a.k.a. The Pigs

2.1.2. Product Owner Strategic Thinking Voice of business Responsibilities Owns Creates and maintains the Product Backlog Chooses what and when to release Represents stakeholders and customers to the Development Team Determines requirements priorities Recommended skills Tolerate and manage change effectively Shift gears/change course quickly and easily Decide and act without having the total picture Tolerate situations where things are up in the air Tolerate and be comfortable with risk and uncertainty May be A Product Manager An executive A personnel manager A customer May NOT be A committee The Scrum Master

2.1.3. Development Team Responsibilities Owns Creates the product Increment Operates in a series of Sprints Organizes itself and its work Collaborates with Product Owner to optimize value Characteristics self-organizing / self-managing cross-functional autonomical intensely collaborative ideally static ideally coolocated recommended size 7 +/- 2 (commnication reasons) May be Software Developer Engineer Tester / QA Architect Graphic Designer Technical Writer May also be Business Analyst Database Specialist User Interaction Designer Requirements Engineer

2.1.4. Scrum Master Responsibilities Owns Enacts Scrum values, practices, and rules throughout the organization Removing the barriers between the development Team and the Product Owner so that the Product Owner directly drives development. Teach the Product Owner how to maximize return on investment (ROI), and meet his/her objectives through Scrum. Improve the lives of the development Team by facilitating creativity and empowerment. Improve the productivity of the development Team in any way possible. Improve the engineering practices and tools so that each increment of functionality is potentially shippable. Keep information about the Team’s progress up to date and visible to all parties. Recommended skills Empathy Inclusive Trustworthy Examine personal ethics May be A manager with appropriate servant-leader skills A member of the Development Team Selected by the Development Team May NOT be A Product Owner

2.2. Stakeholders (selected examples)

2.2.1. a.k.a. The Chickens

2.2.2. Business Owner / CEO

2.2.3. End-Users

2.2.4. Client

2.2.5. Consultants

2.2.6. Rooster a chicken how struts around offering very loud and useless, uninformed opinions / information / input

2.2.7. Any other ...

3. Scrum Events (4)

3.1. Scrum Meetings

3.1.1. Sprint Planning Meeting Watch: Sprint Planning Meeting

3.1.2. Dailiy Scrum Watch: Sprint Planning Meeting

3.1.3. Sprint Review Meeting / Demo Watch: Sprint Planning Meeting

3.1.4. Sprint Retrospective Meeting Watch: Sprint Planning Meeting

4. Agile Techniques (not just in Scrum but general selected techniques in Agile)

4.1. 10 Intristic Motivators

4.2. BDD

4.3. Burn-Down Chart

4.4. Burn-Up Chart


4.6. Circle

4.7. Circles of Concern and Influence

4.8. Daily standups

4.9. Facilitated Workshops

4.10. Feature Progress Report

4.11. Five dysfunctions of a team

4.12. Future Backwards

4.13. Hapiness Door

4.14. Hapiness Index

4.15. Hapiness Metric

4.16. Kanban wall

4.17. Mad, Sad, Glad

4.18. MoSCoW

4.19. Modelling

4.20. Perfection Game

4.21. Personas

4.22. Planning Poker

4.23. Predictability Measure

4.24. Problem -> Goal -> Advantage

4.25. Product / Release Burndown Chart

4.26. Prototyping

4.27. Run your ass off

4.28. Speed dating

4.29. Sprinting / Timeboxing

4.30. Starfish

4.31. Story points

4.32. TDD

4.33. Task boards

4.34. The Sailboat

4.35. Timeline / Emotion Graph

4.36. Velocity

5. Scrum Products / Artifacts (3)

5.1. Product Backlog

5.1.1. What is it? An ordered list of desirements Potential features of the product The single source of truth for what is planned in the product Public and available Has opportunities not commitments

5.2. Sprint Backlog

5.2.1. a.k.a. Team Backlog

5.2.2. Created by the Development Team during Sprint Planning

5.2.3. Often derived by examining and decomposing Product Backlog items (PBIs)

5.2.4. Might be a simple To Do list

5.3. Increment

5.3.1. What is it? The Increment is the sum of all the Product Backlog items completed during the Sprint and all previous Sprints

5.3.2. Is usable and it works

5.3.3. Is potentially shippable

5.3.4. Must be DONE As per Scrum Team standards With no work remaining

5.4. Additional (outside Scrum)

5.4.1. Stories (type of PBIs) User Stories by Client / User Technical Stories by Scrum Team Spike Stories by Scrum Team for research All stories should in line with: INVEST 3C

5.4.2. Product Backlog Item (PBI) What is it? Transparent unit of deliverable work Contains clear acceptance criteria May reference other artifacts like Sized appropriately Valid Product Backlog Items Behaviors Bugs / Defects Chores Constraints Desirements Epics Features definitions Non-functional requirements Prototypes Use Cases User actions or stories

5.4.3. Program Backlog Multiple products, high level Used only in bigger projects

5.4.4. Product / Release Burndown Chart

5.4.5. Sprint Burnup Chart

5.4.6. Sprint Burndown Chart

5.4.7. Sprint Task

6. This freeware mind map was carefully hand crafted with passion and love for learning and constant improvement as well for promotion the Scrum framework and as a learning tool for candidates wanting to gain Scrum PSM qualification. (please share, like and give feedback - your feedback and comments are my main motivation for further elaboration. THX!)

6.1. Questions / issues / errors? What do you think about my work? Your comments are highly appreciated. Please don't hesitate to contact me for :-) Mirosław Dąbrowski, Poland/Warsaw.






6.1.6. miroslaw_dabrowski

7. What is Scrum?

7.1. Scrum (n): A framework within which people can address complex problems, and productively and creatively deliver products of the highest possible value.

7.1.1. Scrum is dedicated for product management not project management

7.2. There is no Scrum methodology, no Agile methodology.

7.3. Scrum is:

7.3.1. One of the agile approaches

7.3.2. Lightweight

7.3.3. Extremely simple to understand

7.3.4. Extremely difficult to master

7.4. Watch: Introduction to Scrum

7.5. The Definitive Guide to Scrum


8. Scrum is a simple framework (not methodology) for effective team collaboration for building complex products (Scrum is not for project management). Scrum provides a small set of rules that create just enough structure for teams to be able to focus their innovation on solving what might otherwise be an insurmountable challenge.

9. Free Scrum Tools Online

9.1. Planning Poker





9.3. Velocity Range Calculator


9.4. Scrumpy


9.5. iceScrum


9.6. Sprintometer


9.7. Scrumy


9.8. PangoScrum

9.9. Online Burndown Chart


9.10. scrumblr


9.11. TaskJunction


10. Scrum Values (5)

10.1. The Scrum values are the values of self-organizing teams.

10.2. Many teams adopt Scrum practices without the Scrum values first ...

10.3. Commitment

10.3.1. Each person is committed to the project's goals

10.4. Respect

10.4.1. Team members respect each other

10.5. Focus

10.5.1. Everyone is focused on the work

10.5.2. A team that’s truly focused is not asked to multitask.

10.6. Openness

10.6.1. Each team member is aware of the work everyone else is doing

10.6.2. The Daily Scrum is all about openness

10.7. Courage

10.7.1. Team members have the courage to stand up for the project

10.7.2. It’s easy to talk about courage, but it’s a lot harder to show it when it means saying no to your boss about an important feature.

11. Agile fundamentals (agile in general not Scrum fundamentals)

11.1. Agile Manifesto


11.1.2. 17 It industry veterans met at Snowbird Resort on February 11-13 2001 and created Agile Manifesto Introduced 4 Values and 12 Principles defining Agile for Software Development

11.1.3. disciplines that gave rise to the Agile Manifesto Extreme Programming, SCRUM, Dynamic Systems Development Method (DSDM®), Adaptive Software Development, Crystal, Feature-Driven Development, Pragmatic Programming.

11.2. Agile Alliance


11.3. Agile currently is buzzword, a marketing term

11.3.1. Agile is like any other newly introduced popular concept. “… Everybody is talking about it. Very few are doing it and those who are, are doing it badly” (James O. Coplien)

11.3.2. Agile as a word by it's own simply means - nothing more than merketing term. there are so many Agile methodologies, Agile standards, Agile techniques, Agile tools, Agile good / best agile practices, Agile frameworks etc., that 'Agile' word itself is to general see Agile World mind map

11.3.3. Agile is a generic description of a “Style of Working” and Philosophy. Not only style of working on project but rather culture in ENTIRE organization including also it's management level, clients and partners ‘Agile Project Management’ is perhaps an oxymoron

11.4. The Agile Mindset, Values and Principles

11.4.1. 4 Agile Value 1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a plan

11.4.2. 12 Agile Principles 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4. Business people and developers must work together daily throughout the project. 5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 7. Working software is the primary measure of progress. 8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9. Continuous attention to technical excellence and good design enhances agility. 10. Simplicity - the art of maximizing the amount of work not done - is essential. 11. The best architectures, requirements, and designs emerge from self-organizing teams. 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

11.4.3. The unlimited number of Agile Practices The 'forest' of Agile Methods, Frameworks, Standards ... see Agile World mind map Being Agile vs Doing Agile

11.5. Agile is a umbrella term enclosing different methodologies, tools, techniques, practices and frameworks

11.5.1. In Agile community umbrella symbolizes different approaches in implementing Agile Manifesto but yet all from them are "Agilelish"

11.5.2. SCRUM, Lean, KANBAN, XP are not ‘Agile Project Management’ practices but rather team level practices No Project Manager role No project definition and etablished project / programme governance ...

11.5.3. see Agile World mind map

11.6. Plan-Driven Projects vs. Change-driven Project Projects

11.6.1. Traditional (waterfall or sequential) Project Management metaphor Railway metaphor Moving forward, based on delivering predicted upfront requirements in accepted tolerances with limited tolerance to change, destination (final product specification) is known upfront and it will hardly change to any other destination Changing course of train based on requirements a.k.a. Plan-driven build around paradigm of process defined process control model All work is understood before execution Given a well-defined set of inputs, the same outputs are generated every time Follow the pre-determined steps to get known results

11.6.2. Agile (iterative + incremental + adaptive) Project Management metaphor Sailing metaphor Embracing change of requirements, finding TRUE value for stakeholders by experimenting, testing, changing status quo. Adapting / changing course of sailing based on business TRUE business needs and priorities, which could be different than requirements a.k.a. Change-driven build around paradigm of change / adaptation empirical (adaptive) process control model Frequent inspection and adaptation occurs as work proceeds Processes are accepted as imperfectly defined Outputs are often unpredictable and unrepeatable

11.7. Agile is best for complex projects

11.7.1. Simple (straightforward) Everything is known and predicatable

11.7.2. Complicated More is known than unknown

11.7.3. Complex More is unknown than known

11.7.4. Chaotic (unpredictable) Very little is known

11.7.5. See also Cynefin framework (by Dan Snowden) different view on Cynefin Framework

11.8. Agile is about delivering "best possible value" not maximum possible value

11.8.1. VALUE is NOT the same as BENEFIT Benefits Benefit is about outputs Benefit is a objective Benefit is an advantage to stakeholders (internal or external to the organization) Benefit can be financial and non financial Benefit can be ... Benefit MUST be measurable and observable Benefits are identifiable and quantifiable Benefits SHOULD have baselines Benefits SHOULD have priorities Benefits types: in general benefit = delivered requirements on time, on budget, within scope etc. Value Value is about outcomes Value is subjective Value can be measurable (if required but not natural to use such techniques in any Agile approach) Value can be ... Values SHOULD have priorities in general value = designed fit for purpose, as small as possible solution

11.9. Agile is about focusing on business value / outcome, not strictly project plan / output

11.9.1. Focusing on value delivery not on fixed product definition or strict adherence to plan That's why most Agile approaches define Project Vision

11.10. Agile respects the urgency and importance of priorities conveyed by the customer / user, most prominently by incremental delivery and flexible sequencing

11.11. Agile respects the common sense that all requirements can not be known at the outset, particularly when the outcomes are intangible and subject to an evolving understanding.

11.11.1. “People don’t know what they want until you show it to them” (Steve Jobs, 1955 - 2011)

11.12. Agile is about empowering people, treating them as intellectual individuals

11.12.1. “You have to learn to manage in situations where you don’t have command authority, where you are neither controlled nor controlling. That is the fundamental change.” (Peter F. Drucker)

11.13. Agile is about working closely and constantly (active two side collaboration) with customer throughout (including more than just feedback loops)

11.13.1. “Never write when you can talk. Never talk when you can nod. And never put anything in an email“ (Eliot Spitzer)

11.14. Agile is about change, constant change which leads to better value

11.14.1. “If a process is too unpredictable or too complicated for the planned, (predictive) approach, then the empirical approach (measure and adapt) is the method of choice“ (Ken Schwaber)

11.14.2. "Move Fast and Break Things" Mark Zuckerberg, Facebook

11.14.3. "Change is the only constant." Heraclitus, Greek philosopher

11.15. Agile thinking / approach often requires mind change and cultural shift

11.15.1. Not every organization is ready for that change!

11.15.2. "It is quite difficult for a highly structured and seniority-based organization to mobilize itself for change, especially under noncrisis conditions. this effort collapses somewhere in the hierarchy" (K. Imai, I. Nonaka, H. Takeuchi)

11.15.3. "Scrum exposes every cultural dysfunction that impedes developing software [...] It is not an approach or process that can be modified to fit the existing organizational culture; the culture must change to enable Scrum" (K. Schwaber, J. Sutherland)

11.15.4. “We cannot become what we need by remaining what we are.” (John C. Maxwell)

11.16. Why Agile Works?

11.16.1. 1. The customer's representative is in the driver's seat

11.16.2. 2. Quick reaction to the changing market and needs

11.16.3. 3. More visibility

11.16.4. 4. Ideal environment for development

11.16.5. 5. Self-manged teams

11.16.6. 6. Removes confusion and distraction

11.16.7. 7. No fortune tellers; Plan as you go

11.16.8. 8. Issues are less disruptive

11.16.9. 9. Continuous improvement