Leanpub Header

Skip to main content

Topics

Project Management

From the first weeks of an inherited project to estimating, critical chain scheduling, Kanban, programmes and the case against projects altogether, project management as told through the free samples of the Leanpub books about it.

Created from the free samples of 11 Leanpub books and the descriptions and tables of contents of 24 more, with every source cited.

Project management is the work of bringing a temporary undertaking to its goal: deciding what is to be delivered, planning and estimating the work, organising the people who do it, watching progress and risk, and keeping those with a stake in the outcome informed and agreed. One practitioner's book puts the purpose of the central activity plainly. A good plan gives the team and its stakeholders a shared view of what they are trying to achieve, how they intend to get there, what it is expected to take and what could upset it; no plan survives contact with reality unchanged, but planning makes uncertainty visible, and a visible risk is one that can be managed.[3]

The discipline grew up in construction, defence and engineering and has spent the last quarter of a century absorbing, and arguing with, the agile methods of the software industry. Most of the books on this shelf come from that industry, and they divide between those that teach the craft, those that replace estimates with forecasts drawn from data, and those that doubt whether software should be managed as projects at all. One of the last kind observes that projects end, and asks who wants their line of business to end.[9]

This article follows the subject from the project manager's job through estimating and forecasting, scheduling and the critical chain, agile delivery and programmes, the case against the project, requirements, stakeholders and reviews, and projects that involve artificial intelligence, with the tools at the end. Its sources are the free samples of the Leanpub books 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 first-time project manager can begin with The Ultimate Guide to Project Management (2016), which starts from the basics and surveys the main systems before turning to software,[12] or with The Complete Guide to Managing Digital Projects (2016), which follows a piece of client work from proposal to invoice.[13] Kanban: A Quick and Easy Guide to Kickstart Your Project (2016) is the quickest way into Kanban.[5] Someone who has just been handed a project already under way has a book written for exactly that month, Project Handover Survival Guide (2026).[1]

The working project manager who is asked for dates has several choices. Predicting the Unpredictable (2015) is a short book on what an estimate is and how to give one,[2] Beyond the Next Sprint (2026) is for those who must plan further ahead than a team that works in sprints naturally does,[3] and When Will It Be Done? (2018) teaches forecasting from a team's own data.[15] Agile and Lean Program Management (2022) is for whoever must coordinate several teams towards one objective.[7]

The advanced reader, and the one responsible for many projects at once, will find the critical chain method in The Book of Dolphins - Part I - (agile) Critical Chain Project Management (2024), which keeps its mathematics in separate chapters,[17] and the theory behind it applied to knowledge work in The Book of TameFlow (2022).[19] Continuous Digital (2021) is for managers ready to question the project model itself.[9]

History

Projects are as old as building, but the discipline dates from the twentieth century: the bar chart for schedules in the 1910s, the critical path method and its relatives in the 1950s for chemical plants and missile programmes, professional bodies and their bodies of knowledge from the 1960s, and government-sponsored methods with stages and boards from the 1980s. Software brought the waterfall model of fixed phases and then, from 2001, the agile methods that deliver in short cycles.

The books give their own versions. Beyond the Next Sprint begins earlier than any of this, with building something, trying it and adjusting it, the oldest method there is and the only one with no plan and no end date.[3] Predicting the Unpredictable recalls that the phases of a serial life cycle existed so that management could cancel a project before it had gone too far, with a deliverable and a fresh estimate at the end of each.[2] Continuous Digital dates the thinking behind functional divisions and cross-cutting projects to the 1960s and the waterfall model to a paper of 1970, and argues that continuous delivery, in which the best teams release many times a day, has since broken the link between the end of a project and the release of software.[9] The Ultimate Guide to Project Management has a short history of its own among its opening chapters.[12]

The project manager's job

Project Handover Survival Guide describes the job at its most exposed, the four weeks after taking over a project in flight, which it names absorb, clarify, plan and deliver. Its author, drawing on some forty handovers, offers two images. The project manager should be a lighthouse, steady and visible, the person stakeholders look to when they want to know whether they are on course, and a falcon, scanning for risks, blockers and silence; a newcomer can play the falcon at once, since fresh eyes see what long-standing members no longer notice. The book applies the rule of the vital few to the takeover: a one-page summary of scope agreed with the sponsor does most of the work of clarity, five half-hour conversations with key stakeholders reveal most of the politics, and the five to seven largest risks account for most of what could derail the project. Trust is treated as the working material. The project manager must be the most predictable person in the room and must delegate, but trust is not blindness, and certain critical figures need checking in person.[1]

The introductions cover the whole cycle. The Ultimate Guide to Project Management is written for the newcomer who feels overwhelmed, and pairs its survey of methods, from the traditional through agile, Kanban and Scrum, with long roundups of project management applications.[12] The Complete Guide to Managing Digital Projects joins the management of a project to the commerce around it: screening a client, giving an estimate, the kickoff meeting, planning and monitoring, tracking time and invoicing.[13] In Engineering Manager’s Compass (2026), a guide to the engineering manager's work, planning and executing projects is one duty among several, with sections on planning for uncertainty, making the plan and carrying it out.[14]

Estimating and forecasting

Predicting the Unpredictable starts from the dictionary: an estimate is a guess. It becomes a better-educated guess as the team learns the domain, the requirements and one another, but it changes as the project changes and it expires. The book distinguishes an accurate estimate, one that turns out within five or ten per cent, from a precise one that names a day and an hour, and says that people who ask how long a project will take want the first. Its advice is to report every estimate with a level of confidence or a range, optimistic, likely and pessimistic. It lists the reasons for estimating, the last of which is that someone wants to know whom to blame, and it is impatient with detailed estimates made for annual budgets: decide how valuable the project is and when the value is needed, tell the team, and let them deliver from a ranked backlog. An order-of-magnitude figure, it says, takes hours and not days.[2]

Beyond the Next Sprint sets seven execution models side by side by where in each the planning happens and what is promised to whom. In waterfall the estimate is made once, up front, when the least is known, and scope, price and date are fixed in a contract; in the staged method of project boards the whole is planned roughly and each stage in detail before the board approves it; in Scrum planning is continuous and the commitment is a sprint goal; in Kanban there is hardly any estimating, since the team counts what it finishes and forecasts from that. The heart of the book is seven estimation techniques, each with the conditions in which it works and fails, followed by scenarios in which agile and classic techniques are combined.[3]

Counting instead of estimating is the method of When Will It Be Done?, which treats every date as a forecast with a probability attached and builds forecasts from the time items have taken and the rate at which they are finished, by simulation where many items are involved.[15] Lean Delivery com Métricas Ágeis (2022), written in Portuguese, covers the estimating of effort, time and cost and the tracking of a first release.[16] Diving For Hidden Treasures (2016) carries the argument to the portfolio. Its sample reviews research on how poorly experts predict complex events, concludes that confidence is no sign of accuracy and that only the short term can be predicted from past behaviour, and proposes that projects be ranked by the cost of delaying them instead of by estimates.[4]

Scheduling and the critical chain

The critical chain is the Theory of Constraints applied to schedules. Where the critical path is the longest sequence of dependent tasks, the critical chain also takes account of the people and resources those tasks compete for, and it removes the safety margin hidden in each task and pools it in buffers. The Book of Dolphins - Part I - (agile) Critical Chain Project Management presents the method for organisations that cannot deliver projects on time, as an introduction, a cookbook and deeper chapters. The cookbook begins with the vicious cycle of too much work in progress and its remedy, staggering projects at the constraint, and goes on to planning, to the sizing of buffers and to the difference between the critical path and the critical chain.[17] A second volume by the same author, Book of Dolphins - Part II - All about TOC and Self-Organization (2025), collects sixteen articles by a former head of a project management office on flow, constraints and self-organisation.[18]

The Book of TameFlow applies the same theory to knowledge work in which there are many projects, deadlines, stakeholders and teams at once, beginning from the five focusing steps: find the constraint, exploit it, and subordinate everything else to it.[19] Its shorter companion, Standing on Bits (2022), proposes that the tangle of dependencies between teams be replaced by a single queue in front of the constraint, with signals from ageing work and from buffers to prompt collaboration.[20]

Agile delivery, Kanban and programmes

Kanban is the lightest of the agile methods to adopt. Kanban: A Quick and Easy Guide to Kickstart Your Project explains it as cards moving across the columns of a board, contrasts a manager pushing tasks to people with team members pulling the next task themselves, and recommends limiting the number of things in hand.[5] Practical Kanban (2019) is for teams whose board exists and is not delivering what was hoped, and extends the method beyond the single team with forecasting and cost of delay.[21] Toolbox for the Agile Coach - Visualization Examples (2015) is a book of examples of the boards themselves, with the advice that a board be placed where the team sits and be simple to keep up to date.[6]

Above the team is the programme. Agile and Lean Program Management defines programmes as strategic collections of projects with one business objective and suggests that the fashionable problem of scaling agile is better understood as scaling projects to a programme. Its principle is to scale collaboration and not process, since copying what works in a small project across a large programme yields bloat, and it asks the programme manager to serve the programme, trusting people and managing by exception. The book is built on principles and not mandates because programmes differ, some of them including hardware and mechanical parts as well as software.[7]

Two books deal with the teams themselves. From Chaos to Successful Distributed Agile Teams (2019) holds that distributed teams succeed through shifts of mindset towards experimentation, collaboration and principles, not through practices copied from teams that share a room, and warns against choosing distribution for reasons of cost.[8] Dynamic Reteaming (2019) starts from the fact that the membership of teams changes whether anyone plans it or not, and describes patterns for adding people, losing them, splitting teams and rotating members.[22]

The case against the project

Continuous Digital argues that the project model does not fit the development of software in a business that depends on it. Its reasons are several. The model assumes that work is temporary, while a line of business built on software needs that software improved for as long as the business lives. It assumes a temporary team, while flexibility comes from having a well-practised team available when needed, each piece of work a rehearsal for the next. And it assumes that lower quality buys speed, while in software the relation is the reverse, since code of higher quality is delivered sooner and more cheaply than code that needs fixing. A company that runs one project after another on the same product, the author says, deludes itself. What the book proposes in place of projects is stable teams and continuing streams of work, a model the author calls a work in progress.[9]

The same impatience appears at the opposite end of the scale. Rethinking Capital Project Delivery (2026) concerns megaprojects in energy and other capital-intensive industries, and argues that stage gates and planning up front lead to overruns that iterative, modular delivery supported by AI would avoid. One of its forewords, by a co-creator of Scrum, holds that the principles which serve software teams can be applied to a refinery or a power plant. The other, by a practitioner of lean methods in an oil company, recalls being told that a capital project is not a conveyor belt, and answering that it is: the project stands still while teams of engineers and contractors pass through it, and productivity is lost at every handover between them.[10]

Requirements, stakeholders and reviews

A project can only deliver what has been described. Exploring Requirements One (2014), subtitled quality before design, is about defining what is wanted before making it: the ambiguity in statements of requirements, getting the right people involved, and running the meetings in which requirements are found.[23] Its second volume, Exploring Requirements Two (2014), goes on to functions, attributes, constraints, preferences and expectations.[24] Stakeholder Engineering: The ‘Stakeholder Systems Engineering’ Discipline (2025), an advanced text from systems engineering, opens with principles: some stakeholders are more critical to a system than others, and they may not know all their needs, or know them precisely.[25]

Agreement is reached in reviews. Handbook of Technical Reviews, Fourth Edition (2014) is a long handbook in questions and answers on reviewing specifications, designs, code and plans, with walkthroughs and inspections among its varieties,[26] and Document Review Toolkit (2026) is a thirteen-page guide to a review meeting that ends in a decision, with a five-step framework, an invitation and an agenda.[27] On what the manager can know about the state of the work, How To Observe Software Systems (2014) holds that many failures of management come from poor observation and sets out the basic measurements an organisation needs,[28] and Perfect Software (2014) treats testing as a search for information made in limited time.[29] Root Cause Analysis (2026) is about what to do afterwards, a programme for finding the causes of recurring problems without assigning blame.[30]

AI projects and tools

Projects that build AI systems have acquired a method of their own. Managing AI Projects with PMI-CPMAI (2026) begins from the claim that such projects fail not because the technology is weak but because they are managed like ordinary software projects, and teaches a life cycle of six phases, from understanding the business need through the data and the model to operation, each ending in deliverables and a decision to continue or stop.[11] AI That Scales (2026) addresses the stage after the pilots, on the view that enterprise AI fails because priorities are vague, costs underestimated and governance late, and has each chapter produce a piece of a roadmap for a board.[31] Stop Implementing AI (2025) describes the same condition from the engineering side as a purgatory of pilots, and answers with a method of planning, phased implementation and testing.[32] Practical Work Delivery with Multiple AIs (2026) shows a single person breaking work into manageable tasks, having one AI tool produce a result and another challenge it.[33]

Two books document particular kinds of project and tool. Building SharePoint Online Intranets (2025) follows an intranet project from the team and the budget through site architecture and migration to the adoption of the result by its users,[34] and Web2project User Manual (2026) is the manual of a web application for managing companies, projects, tasks and task logs, still described as a work in progress.[35]

Questions about Project Management

Which project management book should I start with?

A first-time project manager can begin with The Ultimate Guide to Project Management (2016), which starts from the basics and surveys the main systems, or with The Complete Guide to Managing Digital Projects (2016), which follows a piece of client work from proposal to invoice.[12][13] Someone who has just been handed a project already under way has Project Handover Survival Guide (2026), and the project manager who is asked for dates has Predicting the Unpredictable (2015), a short book on what an estimate is and how to give one.[1][2]

How accurate should a project estimate be?

Predicting the Unpredictable (2015) starts from the dictionary, in which an estimate is a guess, and distinguishes an accurate estimate, one that turns out within five or ten per cent, from a precise one that names a day and an hour.[2] People who ask how long a project will take want the first, it says.[2] Its advice is to report every estimate with a level of confidence or a range, optimistic, likely and pessimistic.[2]

What is the difference between the critical path and the critical chain?

Where the critical path is the longest sequence of dependent tasks, the critical chain also takes account of the people and resources those tasks compete for, and it removes the safety margin hidden in each task and pools it in buffers. The Book of Dolphins - Part I - (agile) Critical Chain Project Management (2024) presents the method for organisations that cannot deliver projects on time, with a cookbook that begins from the vicious cycle of too much work in progress and its remedy, staggering projects at the constraint.[17]

What should I do when I take over a project that is already under way?

Project Handover Survival Guide (2026) describes the four weeks after taking over a project in flight, which it names absorb, clarify, plan and deliver.[1] A one-page summary of scope agreed with the sponsor does most of the work of clarity, five half-hour conversations with key stakeholders reveal most of the politics, and the five to seven largest risks account for most of what could derail the project.[1] A newcomer has one advantage, the book adds, since fresh eyes see what long-standing members no longer notice.[1]

What is a programme in project management?

Agile and Lean Program Management (2022) defines programmes as strategic collections of projects with one business objective.[7] Its principle is to scale collaboration and not process, since copying what works in a small project across a large programme yields bloat.[7] It asks the programme manager to serve the programme, trusting people and managing by exception.[7]

Should software be managed as projects?

Continuous Digital (2021) argues that the project model does not fit the development of software in a business that depends on it.[9] The model assumes that work and teams are temporary, while a line of business built on software needs that software improved for as long as the business lives, and flexibility comes from having a well-practised team available when needed.[9] What the book proposes in place of projects is stable teams and continuing streams of work.[9]

Sources

Every source is a Leanpub book. 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.
    Project Handover Survival Guide, Jens Øster, M.Sc.Eng.: From Chaos to Clarity in Your First 30 Days as a New IT Project Manager Free sample: the preface and the opening sections on the role, the vital few and trust. 2026. Free sample: PDF · EPUB
  2. 2.
    Predicting the Unpredictable, Johanna Rothman: Pragmatic Approaches to Estimating Project Schedule or Cost Free sample: the chapters on what estimates are and why we estimate. 2015. Free sample: PDF · EPUB
  3. 3.
    Beyond the Next Sprint, Jens Øster, M.Sc.Eng.: Long-Term Planning for Agile and Hybrid Projects Free sample: the introduction and the comparison of execution models. 2026. Free sample: PDF · EPUB
  4. 4.
    Diving For Hidden Treasures, Johanna Rothman, Jutta Eckstein: Uncovering the Cost of Delay in Your Project Portfolio Free sample: the opening sections, on prediction and on budgeting. 2016. Free sample: PDF · EPUB
  5. 5.
    Kanban: A Quick and Easy Guide to Kickstart Your Project, Aleksandar Olic Free sample: Kanban basics, push and pull, benefits and getting started. 2016. Free sample: PDF
  6. 6.
    Toolbox for the Agile Coach - Visualization Examples, Jimmy Janlén: How great teams visualize their work Free sample: the welcome, the contents and the general advice on boards. 2015. Free sample: PDF
  7. 7.
    Agile and Lean Program Management, Johanna Rothman: Scaling Collaboration Across the Organization Free sample: the foreword, the introduction and the opening of the first chapter. 2022. Free sample: PDF · EPUB
  8. 8.
    From Chaos to Successful Distributed Agile Teams, Johanna Rothman, Mark Kilby: Collaborate to Deliver Free sample: the close of the first chapter and the contents. 2019. Free sample: PDF · EPUB
  9. 9.
    Continuous Digital, Allan Kelly: An agile alternative to projects Free sample: the opening chapter, on digital business, continuous delivery and products. 2021. Free sample: PDF · EPUB
  10. 10.
    Rethinking Capital Project Delivery, Edward Abramowich: The Owner's Guide to Al-Native Delivery Free sample: the two forewords. 2026. Free sample: PDF
  11. 11.
    Managing AI Projects with PMI-CPMAI, Lamjed CHIHAOUI: A Practitioner's Guide to Delivering AI Projects with PMI-CPMAI Free sample: the introduction, the full contents and the opening of the first chapter. 2026. Free sample: PDF · EPUB
  12. 12.
    The Ultimate Guide to Project Management, Zapier: Learn everything you need to successfully manage projects and get them done No sample: from the description and table of contents. 2016.
  13. 13.
    The Complete Guide to Managing Digital Projects, Aleksandar Olic No sample: from the description and table of contents. 2016.
  14. 14.
    Engineering Manager’s Compass, Dunya Kirkali, Maxim Schepelin: Insights for building effective engineering organizations From the description and table of contents. 2026. Free sample: PDF · EPUB
  15. 15.
    When Will It Be Done?, Daniel Vacanti: Lean-Agile Forecasting To Answer Your Customers' Most Important Question No sample: from the description and table of contents. 2018.
  16. 16.
    Lean Delivery com Métricas Ágeis, Paulo Caroli, Andrea Pinto No sample: from the description and table of contents; in Portuguese. 2022.
  17. 17.
    The Book of Dolphins - Part I - (agile) Critical Chain Project Management, Wolfram Müller No sample: from the description and table of contents. 2024.
  18. 18.
    Book of Dolphins - Part II - All about TOC and Self-Organization, Wolfram Müller No sample: from the description alone. 2025.
  19. 19.
    The Book of TameFlow, Steve Tendon: Theory of Constraints Applied to Knowledge-Work Management No sample: from the description and table of contents. 2022.
  20. 20.
    Standing on Bits, Steve Tendon: Agile Software Engineering Management at Scale with the Theory of Constraints No sample: from the description alone. 2022.
  21. 21.
    Practical Kanban, Klaus Leopold: From Team Focus to Creating Value No sample: from the description and table of contents. 2019.
  22. 22.
    Dynamic Reteaming, Heidi Helfand: The Art and Wisdom of Changing Teams, First Edition No sample: from the description and table of contents. 2019.
  23. 23.
    Exploring Requirements One, Gerald M. Weinberg: Quality Before Design No sample: from the description and table of contents. 2014.
  24. 24.
    Exploring Requirements Two, Gerald M. Weinberg: First Steps to Design No sample: from the table of contents. 2014.
  25. 25.
  26. 26.
    Handbook of Technical Reviews, Fourth Edition, Gerald M. Weinberg No sample: from the table of contents. 2014.
  27. 27.
    Document Review Toolkit, Jens Øster, M.Sc.Eng.: A Professional's Guide to Streamlining Approvals No sample: from the description and table of contents. 2026.
  28. 28.
    How To Observe Software Systems, Gerald M. Weinberg: Software Quality Series: Vol. 3 No sample: from the description and table of contents. 2014.
  29. 29.
    Perfect Software, Gerald M. Weinberg: and other illusions about testing No sample: from the description, which is made up of readers' reviews, and the table of contents. 2014.
  30. 30.
    Root Cause Analysis, Jeremy Berriault The Evolutionary Agilist™: A Practical Guide to Fixing the Real Problem (Without Blame) No sample: from the description and table of contents. 2026.
  31. 31.
    AI That Scales, Luca Berton: Turn AI pilots into a board-ready enterprise AI platform No sample: from the description and table of contents. 2026.
  32. 32.
    Stop Implementing AI, Cliff Robbins: The No-BS Playbook for AI That Works No sample: from the description and table of contents. 2025.
  33. 33.
    Practical Work Delivery with Multiple AIs, William Lee: A step-by-step method for research, presentations and everyday work No sample: from the description and table of contents. 2026.
  34. 34.
    Building SharePoint Online Intranets, Steve Knutson: Practical Advice for building Intranets with SharePoint Online No sample: from the description and table of contents. 2025.
  35. 35.
    Web2project User Manual, Keith Casey: A How To Guide From the description and table of contents. 2026. Free sample: PDF · EPUB

Further reading

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

  • Getting Value out of Agile Retrospectives, Ben Linders, Luis Gonçalves: A Toolbox of Retrospective Exercises A toolbox of exercises for facilitating the retrospectives of agile teams. 2016. Free sample: PDF · EPUB
  • Who is a Product Owner?, Satisha K V: A peek into the Value Maximizer's role! Four short chapters on what a product is, what product management is and how to start as a Product Owner. 2019. Free sample: PDF
  • Agile For Teams, Matt Kocaj A short playbook that prescribes one agile process for a software team. 2018.
  • The Illustrated Guide to Scrum - Volume 2, Peter Stevens: Make Scrum Work for You Infographics on applying Scrum beyond its guide, from sprint planning to estimating. 2024. Free sample: PDF
  • Agile Mix-ins, tom.perry@acm.org: Innovative Prescriptions for Success with Scaled Agile Frameworks A catalogue of practices that can be swapped into scaled agile frameworks. 2025. Free sample: PDF · EPUB
  • Kanban For Lawyers, John E. Grant: The Agile Attorney™ Guide to Law Practice Productivity Kanban for a law practice, from a first board to a limit on work in progress; in progress. 2024. Free sample: PDF · EPUB
  • Agile Constraints Management, Steve Tendon: Agile, Constraints Management and Throughput Economics for Collaborative Knowledge-Work and Software Engineering Management Agile methods combined with the Theory of Constraints and the accounting of throughput. 2026.
  • Idea Flow, Janelle Arty Starr: How to Measure the PAIN in Software Development A technique for mapping the friction developers meet, so that a team's largest problems can be shown as data. 2019. Free sample: PDF · EPUB
  • Practical Ways to Lead an Innovative Organization, Johanna Rothman: Modern Management Made Easy, Book 3 Questions and myths of management, each with options, from a series on modern management. 2020. Free sample: PDF · EPUB
  • Becoming a Change Artist, Gerald M. Weinberg: Volume 7: Quality Software Series Models of how change happens in software organisations and how to support it. 2014.
  • Why Software Gets In Trouble, Gerald M. Weinberg: Software Quality Series: Vol. 2 How software organisations notice errors and failures, and what pressure does to performance. 2016.
  • Errors, Gerald M. Weinberg: Bugs, Boo-boos, Blunders Software errors: what they cost, where they come from and how to prevent them. 2017.
  • What Drives Quality, Ben Linders: A Deep Dive into Software Quality with Practical Solutions for Delivering High-Quality Products -- Second Edition A model of the factors that drive software quality, from requirements to project management. 2018. Free sample: PDF · EPUB
  • The forgotten new philosophy of work, management & leadership, Luca Minudel Why some projects cannot be reliably estimated, planned or controlled, from the standpoint of complexity science. 2025. Free sample: PDF · EPUB
  • Succeed over difficult problems by embracing Complexity-Thinking, Luca Minudel: Micro-guide to thriving in everyday complexity by breaking free from ordered and linear approaches A short guide to telling complex problems from complicated ones and acting on the difference. 2025. Free sample: PDF · EPUB
  • OKR, the right way, Francesco Fullone: Allineare persone e strategia senza perdere il senso A practical guide to objectives and key results, written in Italian. 2026.

This is an article created from the free samples of 11 Leanpub books and the descriptions and tables of contents of 24 more. 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: 473 books · 3 courses in the Project Management category · also filed under Risk Management

All topics