Leanpub Header

Skip to main content

Topics

Scrum

From the accountabilities, events and artefacts of the framework to retrospectives, user stories, flow metrics, scaling and Scrum teams of AI agents, Scrum as told through the free samples of the Leanpub books about it.

Created from the free samples of 9 Leanpub books and the descriptions and tables of contents of 36 more books and courses, with every source cited.

Scrum is a framework for developing products in short, fixed cycles called sprints, in which a small team repeatedly plans a piece of work, builds it, shows it and reflects on how the work went. It prescribes little: three accountabilities, the Product Owner who decides what is most valuable, the Scrum Master who looks after the process, and the developers who do the work; a handful of events within each sprint; and three artefacts, the chief of them the ordered list of work called the product backlog. One training manual in the library gives the argument for it in a word, speed, and says that companies shorten their response and delivery times by replacing states of waiting with a structure for rapid decisions, with a regular cycle of inspection and adaptation to compound the effect.[2]

Scrum is the most widely used of the agile methods and for that reason the most widely misused, and much of the writing about it is corrective. A coach's book opens with a Scrum Master whose planning meetings, retrospectives and charts are all exemplary while nothing reaches customers any faster, and locates the fault not in Scrum but in treating it as a ritual to follow instead of a tool for creating flow.[5] The library accordingly holds, beside its introductions, books on each event taken singly, on the two leading roles, on forecasting without estimates, on work that spans many teams, and a set of volumes that go back to what their author calls first principles.

This article follows the subject from the framework itself through the Scrum Master, the events in practice, the Product Owner and the backlog, estimation and forecasting, Scrum beyond a single software team, first principles and teams of AI agents, and the doubts practitioners raise. Its sources are the free samples of the Leanpub books and courses listed at the end, with the descriptions and tables of contents of those whose samples were not available or not read, and every claim that rests on a source is cited to it.

Where to start

A newcomer can begin with The Illustrated Guide to Scrum (2024), which explains the framework in infographics, each with a page of explanation,[1] or with Why is this so hard? Mastering Scrum and Agile (2022), an informal book of stories and tips that needs no prior knowledge and can be read in any order.[11] Scrum Master (2023) is a training seminar in book form for business leaders and professionals.[2] The vocabulary can be looked up in Lingo: Agile, an alphabetical glossary of agile terms.[12]

Someone about to take on a role has books addressed to it. Scrum Master Essentials (2026) is a short manual for a Scrum Master or project manager setting up a team in a traditional company,[4] and Conquering Product Ownership (2021) serves both those working as Product Owners and those preparing for the certification.[22]

The practitioner with some experience is the reader of the books on single practices: Effective Sprint Planning (2021) says of itself that it is not an introduction to Scrum,[16] and Flow Metrics for Scrum Teams (2023) is for teams that want to spend less time estimating.[25] First Principles in Scrum (2024) and its companion volumes are for Scrum Masters, Product Owners and managers who want the reasoning behind the practices.[37]

History

The name comes from rugby, by way of a 1986 article on product development in Japanese manufacturing that likened the best teams to a scrum moving the ball up the field together. Jeff Sutherland and Ken Schwaber applied the idea to software in the early 1990s and presented Scrum publicly in 1995; both signed the Agile Manifesto in 2001, and the short guide in which they define the framework has been revised several times since.

The books show where it has gone. Five volumes on the shelf appear under Sutherland's name, the first of them prompted, its description says, by the dozens of questions about Scrum he is asked each week by new Product Owners and Scrum Masters.[37] The manufacturing origin has come round again in books that take Scrum back to hardware,[34] and the newest volumes apply it to teams made up partly of software agents.[41] One manual measures the distance travelled in tools: when its author began, in 2008, a spreadsheet was considered advanced.[4]

The framework

The Illustrated Guide to Scrum presents the framework as its guide does, in three parts: the Scrum Team and who is accountable for what, the Sprint and its events, and the artefacts with the definition of done. Each topic is one infographic with a page of explanation on the reverse, laid out so that the pages can be printed as posters or as handouts for a class, and the author's stated wish is to share what he calls the joy and simplicity of Scrum, which by his own account turned a mediocre project manager into a good Scrum Master.[1] The Illustrated Guide to Scrum - Volume 2 continues in the same form for practitioners who know the basics, with pages on such questions as whether it is acceptable to change Scrum and what a project manager would contribute to a Scrum team.[10]

The other introductions each choose a manner. Scrum Master is organised as sprints of five chapters and argues from cases in manufacturing; it is careful to say that speed is not always what a customer wants, setting a convenience store on a busy street beside a secluded bathhouse. Its later chapters cover estimation, the planning of releases and sprints, practices for hardware, the conversion of a whole company and the certifications.[2] The Scrum Canvas gives newcomers a set of canvases and templates for facilitating each kind of session.[13] Speaking of Agile collects metaphors and analogies for explaining the ideas to colleagues,[14] and Follow ... the path of Ray, Howard, and Britta is a novel in episodes, in which a Product Owner, a Scrum Master and a coach at an invented company prepare a product for a trade fair, each episode followed by a discussion of the problem it raised; in the sample the trouble is a poster from the marketing department that promises features the sprint does not contain.[8]

The Scrum Master

The role is the hardest to describe, since it has no authority over the work, and the books describe it mostly by its failures. Scrum Master Essentials names two: the Scrum Master who treats the team as a group of friends and admits every new request into the sprint, and the one who treats the guide as a law book and refuses urgent business in order to protect the sprint. The path between them is a habit of trade-offs, so that when something critical arrives in mid-sprint the question asked is what will be taken out to make room. The same preface holds that a Scrum Master should aim to become unnecessary, with the team removing its own impediments and running its own events, and the book supplies a launch guide in eleven steps for a team in a traditional company, with ready-made invitations for each of the events and an early section on when Scrum fits a piece of work and when it does not.[4]

Stop Facilitating, Start Leading (2026) asks more of the role. It follows three invented practitioners who facilitate well and deliver slowly, one of whom maps fourteen weeks of waiting between work being called done and its reaching production, and it proposes that the Scrum Master measure the time from idea to effect and not the team's velocity. Its author notes that the book was written with the assistance of AI.[5] 89 Tips From The agile Trenches (2021) gathers short pieces of advice for Scrum Masters and coaches from 89 practitioners in 28 countries, arranged under the phrases of the agile manifesto and ranging over coaching, retrospectives, the refinement of the backlog, the dynamics of teams and remote work.[15]

Planning, the daily scrum and the retrospective

Three of the events have books to themselves. Effective Sprint Planning is about preparing for and running the planning meeting so that a team knows what it is building, why and how, through principles and techniques that need no special tools.[16] The FOCUSED Daily Stand-Up (2024) explains the purpose of the daily meeting through an acronym, a chapter to each letter.[17]

The daily scrum is also the first example in Scrum First Aid (2020), a book of problems and remedies in which each chapter starts from a practitioner's question. A developer describes a team whose members stand and report, for every task, its number, its original estimate, the actual time and the reason for the difference, and asks whether this is Scrum. The answer is that it is a traditional status report under another name, and that telling the two apart is an almost universal difficulty for teams arriving from a process of command and control. The book's introduction adds that adoption fails without the support of leadership.[3]

The retrospective, the meeting in which a team examines its own way of working, has the largest literature. Plans for Retrospectives (2026) offers fifteen complete plans of sixty to ninety minutes, each matched to a situation such as a new team or a complaining one, for facilitators who find it hard to assemble a session from separate activities.[18] The Retrospective Playbook - The Format Plays sets out formats as plays to try and adapt, with templates;[19] 10 Experiments for Better Retrospectives presents ten formats as experiments, grouped by the stage of development a team has reached, against what it calls death by stop, start, continue;[20] and Corinna's Guide to Facilitating Retrospectives is one practitioner's own routine, described as if to a new colleague.[21]

The Product Owner and the backlog

The Product Owner decides what the team builds next. Conquering Product Ownership treats the role in three parts: the theory, roles, artefacts and events of Scrum; the vision, strategy, roadmap and measures of value for a product; and the daily work of managing a backlog, gathering requirements and planning releases.[22] A short course, Long term Product Goals for creating superior products, is about the long-term goals and visions towards which a backlog is ordered.[23]

The backlog is made of user stories. Crafting User Stories That Truly Deliver (2026) defines one as an informal description of a user's need that settles three things, who has the need, what they want to achieve and why, and holds that stories come from conversations with users in which the Product Owner does not ask what people want but accompanies them in discovering it. The questions it suggests are about the user's work and not about software: what their daily objectives are, which are not yet being met, and what they need to complete.[7] Vertical Slicing and How to Boost Value Delivery is about splitting a story so that each piece passes through every layer of the system and can be finished and delivered by itself.[24] Ready (2026) addresses work that enters a sprint half understood, proposing three practices for maturing requirements before and during implementation; its image for a team with a full backlog and no shared picture is a jigsaw puzzle attempted without the picture on the box.[9]

Estimation and forecasting

When will it be done is the question Scrum teams are asked most, and the traditional answer, estimating each story in points, is under attack on this shelf. Flow Metrics for Scrum Teams, the most widely read book here, carries its thesis in its subtitle, that story points were never a part of Scrum. It replaces them with four measures, the work in progress, the time an item takes, the age of items not yet finished and the number completed in a period, and shows how each is used in the events of the sprint to forecast in probabilities.[25] Software Estimation (2025), by a coach of technology executives, holds that most estimation of software is waste and sets out the few reasons for which it is worth doing.[26]

Beyond Burnups (2026) takes forecasting further, from the burnup chart to simulation, and is frank that simulation is not the end of the matter, since several features in progress at once and dependencies between teams quietly break it.[27] The older method is taught in a video course, Rapid Estimating & Merciless Tracking, which builds the charts for tracking progress against a release from a spreadsheet,[28] and Beyond the Next Sprint (2026) is about planning a quarter to a year ahead when the team works in sprints and a sponsor wants a long-term plan.[29]

Beyond one software team

Scrum describes one team, and most organisations have many. SAFe to Scale (2025) is a guide for product managers and Product Owners to one scaling framework, with its planning event for many teams at once and its shared backlog.[30] Two books by one author approach the same problem from the theory of constraints, The Book of TameFlow at length and Standing on Bits in brief, with prioritisation on financial grounds and a single queue in front of the constraint when there are many projects, stakeholders and teams.[31][32] A Very Brief (but sufficient) Guide to Running a Managing Dependencies Workshop is a guide to running one workshop, in which teams find, sort and rank their dependencies on one another.[33]

Other books carry Scrum to other kinds of work. Scrum for Hardware Explained (2024) is written for manufacturing, from a pilot team and an agile architecture to several teams, vendors and production.[34] Scrum in AI (2023), by the same author, combines Scrum with the engineering practices of machine learning for teams building AI applications, and ends with coaching conversations about particular projects.[35] Agile and Scrum for QA: Quality in Every Sprint (2026) looks at the sprint from the tester's seat: the tester is no longer a gatekeeper who approves or rejects work at the end but an advocate for quality who shapes how work is defined and verified from the start. In the older arrangement, as the book describes it, developers threw code over a wall and testers threw defects back, the relation was adversarial and testing was a bottleneck by design; the tester's question has changed from whether a thing works to how the team can make sure it will before building begins.[6] And An Agile Playbook for Technical Communicators (2025) shows writers of documentation how to fit their work into sprints.[36]

First principles and teams of agents

First Principles in Scrum is a long collection of essays whose premise is that most questions about Scrum cannot be answered from the rules of the framework and must be taken back to physics, biology and other sciences, with complex adaptive systems and the behaviour of teams under uncertainty as recurring themes, mixed with its author's own stories.[37] Three later volumes divide the material: First Principles in Scrum: Foundations on the theory,[38] First Principles in Scrum: Implementing Scrum and Agile Practices on the reasons for particular practices, with case studies,[39] and First Principles in Scrum: Advanced Strategies and Reflections on strategy and leadership, drawing on fields as distant as warfare and architecture.[40]

The newest application is to artificial intelligence. First Principles in Scrum: OpenClaw Scrum and Scrum@Scale (2026) describes an operating model in which AI agents are treated as members of a Scrum team under the same empirical control as people, with the structures of scaled Scrum coordinating teams of humans and agents, and it catalogues the ways such teams fail.[41] A shorter report by the same author, Hermes: Organizations as Swarming Agents, argues that several agents organised as a Scrum team finish more work at lower cost than a single agent; the figures are its own.[42]

Doubts and corrections

The shelf does not speak with one voice. Real World Agility (2025) announces that it is not about Scrum or any other framework, and judges agile working by its outcomes and not by velocity or counts of features, with case studies that include failures.[43] The Void in Agile is an engineer's account of the gaps in how agile methods are practised.[44] And Quicksands of software development, written as a warning to people early in a programming career, counts Scrum among the non-technical frustrations of the trade, beside estimates, deadlines and meetings.[45] The remedies proposed elsewhere on the shelf are mostly of one kind, to stop performing the events and start measuring whether anything reaches the customer sooner.[5][25]

Questions about Scrum

Which Scrum book should I start with?

A newcomer can begin with The Illustrated Guide to Scrum (2024), which explains the framework in infographics, each with a page of explanation, or with Why is this so hard? Mastering Scrum and Agile (2022), an informal book of stories and tips that needs no prior knowledge.[1][11] Someone about to take on a role has Scrum Master Essentials (2026), a short manual for a Scrum Master or project manager setting up a team in a traditional company, or Conquering Product Ownership (2021), for those working as Product Owners and those preparing for the certification.[4][22]

What is Scrum?

Scrum is a framework for developing products in short, fixed cycles called sprints, in which a small team repeatedly plans a piece of work, builds it, shows it and reflects on how the work went. It prescribes three accountabilities, the Product Owner, the Scrum Master and the developers, a handful of events within each sprint, and three artefacts, the chief of them the ordered list of work called the product backlog. Scrum Master (2023) gives the argument for it in a word, speed: companies shorten their response and delivery times by replacing states of waiting with a structure for rapid decisions.[2]

What does a Scrum Master do?

Scrum Master Essentials (2026) describes the role by its two failures: the Scrum Master who treats the team as a group of friends and admits every new request into the sprint, and the one who treats the guide as a law book and refuses urgent business in order to protect the sprint.[4] The path between them is a habit of trade-offs, so that when something critical arrives in mid-sprint the question asked is what will be taken out to make room.[4] The same book holds that a Scrum Master should aim to become unnecessary, with the team removing its own impediments and running its own events.[4]

Is the daily scrum a status meeting?

Scrum First Aid (2020) takes the question from a developer whose team stands and reports, for every task, its number, its original estimate, the actual time and the reason for the difference.[3] The book's answer is that this is a traditional status report under another name, and that telling the two apart is an almost universal difficulty for teams arriving from a process of command and control.[3] The FOCUSED Daily Stand-Up (2024) explains the purpose of the daily meeting through an acronym, a chapter to each letter.[17]

Are story points part of Scrum?

Flow Metrics for Scrum Teams (2023) carries its answer in its subtitle, that story points were never a part of Scrum.[25] It replaces them with four measures, the work in progress, the time an item takes, the age of items not yet finished and the number completed in a period, and shows how each is used in the events of the sprint to forecast in probabilities.[25] Software Estimation (2025) holds that most estimation of software is waste and sets out the few reasons for which it is worth doing.[26]

What is a user story?

Crafting User Stories That Truly Deliver (2026) defines one as an informal description of a user's need that settles three things: who has the need, what they want to achieve and why.[7] Stories come, it holds, from conversations with users in which the Product Owner does not ask what people want but accompanies them in discovering it.[7] Vertical Slicing and How to Boost Value Delivery is about splitting a story so that each piece passes through every layer of the system and can be finished and delivered by itself.[24]

Sources

Every source is a Leanpub book or course. The note after each says which part of it was read; where no sample was available, only the public description and table of contents were used.

  1. 1.
    The Illustrated Guide to Scrum, Peter Stevens: Volume 1: Inside the Scrum Team Free sample: the contents, the author's letter and the opening pages on the Scrum Team. 2024. Free sample: PDF
  2. 2.
    Scrum Master, Joe Justice: The Agile Training Seminar for Business Performance Free sample: the chapter list and the chapter on the business case for agile methods. 2023. Free sample: PDF
  3. 3.
    Scrum First Aid, Todd A. Jacobs: A Recipe Book for Fixing Scrum Challenges and Anti-Patterns Free sample: the introduction and the chapter on the Daily Scrum used as a status report. 2020. Free sample: PDF · EPUB
  4. 4.
    Scrum Master Essentials, Jens Øster, M.Sc.Eng.: Build your team from scratch and drive results that matter Free sample: the preface, on the two extremes of the role, and the introduction. 2026. Free sample: PDF · EPUB
  5. 5.
    Stop Facilitating, Start Leading, Tristan Libersat: The Scrum Master's Path to Value Flow Management Free sample: the preface and the opening stories of three practitioners. 2026. Free sample: PDF · EPUB
  6. 6.
    Agile and Scrum for QA: Quality in Every Sprint, Yuri Syuganov: Sprint Planning, Ceremonies, and the QA Mindset Free sample: the introduction and the first chapter, on the tester as gatekeeper and as quality coach. 2026. Free sample: PDF
  7. 7.
    Crafting User Stories That Truly Deliver, Edgar Fernandez Free sample: the definition of a user story and the section on finding stories in conversation. 2026. Free sample: PDF
  8. 8.
    Follow ... the path of Ray, Howard, and Britta, René Schröder: An Essential Tale of Agile Transformation Strategy Free sample: the front matter and one episode with its discussion. 2022. Free sample: PDF · EPUB
  9. 9.
    Ready, Luniel de Beer, Max Guernsey, III: Why Most Software Projects Fail and How to Fix It Free sample: the front matter and the opening of the second chapter. 2026. Free sample: PDF · EPUB
  10. 10.
    The Illustrated Guide to Scrum - Volume 2, Peter Stevens: Make Scrum Work for You From the description and table of contents. 2024. Free sample: PDF
  11. 11.
    Why is this so hard? Mastering Scrum and Agile, Mark H. Faulkner No sample: from the description and table of contents. 2022.
  12. 12.
    Lingo: Agile, Samuel Gregory: A simplified look at Agile terms you actually need From the description and table of contents. 2022. Free sample: PDF · EPUB
  13. 13.
    The Scrum Canvas, Fadi Stephan: Tools and Templates for New Scrum Practitioners No sample: from the description alone. 2022.
  14. 14.
    Speaking of Agile, Rich Brents: How rhetorical devices like metaphors and analogies can help make clear the changes needed to adopt an Agile mindset No sample: from the description and table of contents. 2021.
  15. 15.
    89 Tips From The agile Trenches, YvesHanoulle: for scrummasters & agile coaches No sample: from the description and table of contents. 2021.
  16. 16.
    Effective Sprint Planning, Clayton Lengel-Zigich: How to actually run a (successful) sprint planning meeting No sample: from the description and table of contents. 2021.
  17. 17.
    The FOCUSED Daily Stand-Up, Robin Hackshall No sample: from the description and table of contents. 2024.
  18. 18.
    Plans for Retrospectives, Corinna Baldauf No sample: from the description and table of contents. 2026.
  19. 19.
    The Retrospective Playbook - The Format Plays, Chris Stone: Levelling up your Continuous Improvement Game No sample: from the description alone. 2023.
  20. 20.
    10 Experiments for Better Retrospectives, Daniel Scheufler No sample: from the description and table of contents. 2025.
  21. 21.
    Corinna's Guide to Facilitating Retrospectives, Corinna Baldauf: For Beginners No sample: from the description and table of contents. 2026.
  22. 22.
    Conquering Product Ownership, Hannah Farrugia: A smart sidekick to help you prepare for your PSPO™ Certification No sample: from the description and table of contents. 2021. Free sample: PDF
  23. 23.
    Long term Product Goals for creating superior productsCourse, Allan Kelly: How to create and use product goals, product vision, north stars and true norths to deliver winning products A course; no sample: from the description alone. 2026.
  24. 24.
    Vertical Slicing and How to Boost Value Delivery, TJ Rerob: Slicing user stories in Agile software development No sample: from the description and table of contents. 2021.
  25. 25.
    Flow Metrics for Scrum Teams, Daniel Vacanti, Will Seele: Because story points were never a part of Scrum anyway No sample: from the description and table of contents. 2023.
  26. 26.
    Software Estimation, Stephan Schmidt: Estimation that Works No sample: from the description and table of contents. 2025.
  27. 27.
    Beyond Burnups, Nicolas Brown: The different ways to forecast delivery (and when to use them) No sample: from the description alone. 2026.
  28. 28.
    Rapid Estimating & Merciless TrackingCourse, Tom Steele: Begin your hero's journey to get your project on track... Your stakeholders will love it... A course; no sample: from the lesson titles. 2020.
  29. 29.
    Beyond the Next Sprint, Jens Øster, M.Sc.Eng.: Long-Term Planning for Agile and Hybrid Projects From the description and table of contents. 2026. Free sample: PDF · EPUB
  30. 30.
    SAFe to Scale, Valerio Zanini: The Practical Guide to Scaled Agile for Product Managers and Product Owners No sample: from the description and table of contents. 2025.
  31. 31.
    The Book of TameFlow, Steve Tendon: Theory of Constraints Applied to Knowledge-Work Management No sample: from the description and table of contents. 2022.
  32. 32.
    Standing on Bits, Steve Tendon: Agile Software Engineering Management at Scale with the Theory of Constraints No sample: from the description alone. 2022.
  33. 33.
    A Very Brief (but sufficient) Guide to Running a Managing Dependencies Workshop, Paul Klipp No sample: from the description and table of contents, which marks several chapters as drafts. 2023.
  34. 34.
    Scrum for Hardware Explained, Paolo Sammicheli: Achieving Industrial Agility No sample: from the description and table of contents. 2024.
  35. 35.
    Scrum in AI, Paolo Sammicheli: Artificial Intelligence Agile Development with Scrum and MLOps No sample: from the description and table of contents. 2023.
  36. 36.
    An Agile Playbook for Technical Communicators, Luke Pivac: A Guide for Technical Communicators Working with Agile Teams No sample: from the description and table of contents. 2025.
  37. 37.
    First Principles in Scrum, Jeff Sutherland: Teams That Finish Early Accelerate Faster No sample: from the description and table of contents. 2024.
  38. 38.
    First Principles in Scrum: Foundations, Jeff Sutherland No sample: from the description and table of contents. 2026.
  39. 39.
    First Principles in Scrum: Implementing Scrum and Agile Practices, Jeff Sutherland, Ph.D. No sample: from the description and table of contents. 2026.
  40. 40.
    First Principles in Scrum: Advanced Strategies and Reflections, Jeff Sutherland No sample: from the description and table of contents. 2026.
  41. 41.
    First Principles in Scrum: OpenClaw Scrum and Scrum@Scale, Jeff Sutherland: Create Trust at Machine Speed No sample: from the description and table of contents. 2026.
  42. 42.
    Hermes: Organizations as Swarming Agents, Jeff Sutherland No sample: from the description and table of contents. 2026.
  43. 43.
    Real World Agility, Nicolas Brown: Backed by evidence, built for results No sample: from the description alone. 2025.
  44. 44.
    The Void in Agile, Lakshmi Kanth Vallampati: Unveiling the gaps in today’s agile practices No sample: from the description and table of contents. 2025.
  45. 45.
    Quicksands of software development, D. Petre Bogdan From the description and table of contents. 2022. Free sample: PDF · EPUB

Further reading

Other books in the library on neighbouring ground, not cited above.

  • The Cybernetic Enterprise, Romano Roth: How to Build a Future-Ready Organization An operating model for large organisations that combines agile methods, DevOps and platform engineering around feedback loops. 2025.
  • Project Lifecycles, Johanna Rothman: How to Reduce Risks, Release Successful Products, and Increase Agility Choosing and designing a project lifecycle from the risks of the project, on the view that neither waterfall nor agile fits every case. 2023.
  • Principles of Project Management, Adam Russell: The Building Blocks of Agility Numbered principles and heuristics for software projects under any lifecycle. 2024.
  • Teaching Team Collaboration, Bruce Scharlau: The Human Side of Software Development For those who teach software development: phases, rules and classroom examples for guiding student teams. 2023.
  • Deliver What Matters When It Matters, Ryan Kent: Value-Driven Product Delivery through Clarity, Timing, and Flow A model for delivery built on clarity of value, effectiveness of flow and timing. 2026. Free sample: PDF
  • 10 Days to Greater Agility, Daniel Scheufler A ten-day challenge of small daily actions for practising the agile mindset. 2025.

This is an article created from the free samples of 9 Leanpub books and the descriptions and tables of contents of 36 more books and courses. We're building these articles to provide you, the Leanpub reader, with a good jumping-off point to discover more Leanpub books that are interesting and relevant to you. We never use material which is paid-only when building these articles: we only use material which is already free on Leanpub. However, Leanpub authors can opt out from inclusion in articles from their book settings page.

Updated November 2026.

In the Leanpub store: 256 books · 3 courses in the Scrum category · also filed under Scrum

All topics