Pro Kit · e-book + tools27 filesAbout 3 hours to read

Run Scrum or Kanban with the method, files and numbers to improve delivery

A hands-on kit for new Scrum Masters, team leads, Product Owners and students: the method, the working files and the numbers to prove it, in software or business teams.

  • A 12-chapter guide that follows one team from a ticket queue to six sprints, with every number in the 22-sheet workbook
  • A practice pack that runs here and on your laptop: cycle-time calculator with Monte Carlo forecast, burn-up, story checker and backlog converter
  • Sample backlog import files for Jira and Asana, plus a Trello paste file, with dated tool notes and official links
  • Six fillable forms, eight Word templates, 30 messages, 25 AI prompts, 9 casebook scenarios and a 14-question knowledge check

The Agile and Scrum Team Kit · Bodhih Pro Kits · 361 by Bodhih Training, trainers to 2,000+ companies since 2008.

Quick answer

How do I run a team with Scrum or Kanban?

Agree one goal, name one Product Owner, limit work in progress, plan short sprints from real capacity, review working results with users and improve one or two things each time. The Agile and Scrum Team Kit by Bodhih Training gives you the method, a 22-sheet workbook, a cycle-time calculator and import files for Jira, Asana and Trello.

Want the full free guide first? Read How to run a Scrum or Kanban team: sprints, WIP limits and cycle time explained.

Sound familiar?

You already feel the problem. Here is what it is costing you.

Everything is in progress, little is finished

The board is full, everyone is busy, and the oldest item has been 'in progress' for weeks. Without limits on work in progress, starting feels like progress while finishing slows down.

Ceremonies without results

Stand-ups became status meetings, sprints end with half the work carried over, and retrospectives repeat the same complaints. The events are there; the ideas behind them are not.

No honest answer to 'when will it be done?'

Leaders want a date, the team wants to avoid a promise, and velocity charts get used to judge people. You need a forecast range built from your own data.

Now imagine this

Picture the next few weeks with the kit open beside you.

Picture your next Monday. Instead of a list of open tickets, you open the workbook, capture your baseline and see exactly where work is waiting. As you run the cycle-time calculator, the numbers stop being opinions.

Two weeks later you plan the first sprint from real capacity, with one Sprint Goal a stakeholder understands. The board has a WIP limit. When the column fills up, the team swarms instead of starting something new.

At the sixth Sprint Review you show four numbers: a burn-up forecast range, median cycle time against the baseline, Sprint Goals met and escaped defects. In the kit's worked example the median fell from 15 days to 4.5. Your numbers will be your own, and you will be able to show them.

Whether you start with the 15-minute quick start tonight or the charter session next week, every step has a file ready to fill.

What’s in the box

27 files that do the work for you

The e-book shows you how. The tools make it happen. Here is exactly what you download.

E-book

The Agile and Scrum Team Kit (e-book, PDF)

The guide: methods, worked examples, scripts and exercises

🔒
Cheat sheet

Start here: agile team map

The whole job in ten steps with the file to open for each, a 15-minute quick start, your first hour, your first week, the six-sprint plan and the 'brand it in five minutes' box.

🔒
Cheat sheet

Situation router: which files to open, in which order

14 common situations, each with the files to open in order, plus the 15-minute quick start.

🔒
Spreadsheet

Agile Team Master Workbook

22 sheets: Settings, Self-assessment and Gap plan, Backlog with READY check, Capacity, Sprint log, Flow log (89 SAMPLE items), Flow summary, Burn-up forecast, Retro actions, Impediments, Decision log, Readiness check, Dashboard with four charts and traffic lights, Tool notes, Crosswalk, RACI, Roadmap, What changed, Glossary and Sources.

🔒
Spreadsheet

Business case calculator (low, expected, high, do nothing)

Four cases with one-off and running costs, observable benefits (rework avoided, reporting time saved, earlier delivery), net per month, break-even month and a 24-month cumulative chart. Low case first: it is allowed not to pay back.

🔒
Fillable PDF

Team charter and working agreement

One page the whole team signs before Sprint 1: purpose, Product Goal, who holds each accountability, cadence, working agreements, Definition of Done summary and how decisions get made.

🔒
Fillable PDF

User story and acceptance criteria worksheet

Write one story the team can plan, build and test: the three parts, the INVEST check, 2-5 acceptance criteria in Given/When/Then form, a size and a splitting plan.

🔒
Fillable PDF

Sprint planning worksheet

The three Sprint Planning topics on one page: why (Sprint Goal), what (items chosen against capacity and recent velocity) and how (first tasks, risks, dependencies).

🔒
Fillable PDF

Sprint review and retrospective record

Record the Sprint Review as a working session (what was done, feedback, backlog changes, forecast) and the retrospective (format, insights, 1-2 owned actions, last sprint's actions).

🔒
Fillable PDF

Kanban board design worksheet

Design a Kanban system for any team: work item types, start and finish points, columns, WIP limits, explicit policies, service level expectation and the meetings that keep it flowing.

🔒
Fillable PDF

Readiness check: start Sprint 1 (go / no-go)

Go or no-go before the first sprint (or a re-start): critical criteria, evidence and the verdict, matching the workbook's Readiness check sheet.

🔒
Word template

Leadership sign-off and decision memo

A one-page memo for the sponsor: the problem in numbers, the six-sprint trial, what the team needs, what leaders get, the low and expected business cases, risks and the decision with signatures.

🔒
Word template

Agile ways of working policy (policy starter)

A short policy starter that leaders can adopt: scope, principles, accountabilities, how work enters teams, events, quality, metrics use, tools and data, AI use, review.

🔒
Word template

Definition of Done and sprint cadence procedure (procedure starter)

Step-by-step procedure for a two-week sprint (day by day), plus a Definition of Done template for software and non-software teams and how to change it.

🔒
Word template

Message and email library (30 messages)

30 ready-to-adapt messages for kick-off, backlog requests, protecting the sprint, escalating impediments, Sprint Reviews, sponsor reports, retrospectives and metrics conversations.

🔒
Word template

Worked examples: Marcus's filled templates

The three most-used templates filled in by the persona with consistent numbers: the Sprint 2 planning worksheet, a user story with acceptance criteria (photo upload), and the Sprint 1 review and retrospective record.

🔒
Word template

Scenario casebook (9 cases with model answers)

9 realistic cases (US, Canada, Ireland, UK, Germany, India-US, Australia, New Zealand; software and non-software; 4 to 10 people) with questions and model answers that use the kit's method and files.

🔒
Word template

AI prompt pack for agile teams (25 prompts)

25 tool-agnostic prompts for stories, splitting, acceptance criteria, refinement, forecasts, Sprint Goals, reviews, retrospectives, metrics and stakeholder messages, each with a human check and the review rules.

🔒
Word template

45-minute team briefing plan and knowledge-check answer key

A ready-to-run 45-minute session to brief your team before Sprint 1: agenda with timings, what to say, two activities, materials list, the knowledge-check CSV instructions and a printable answer key.

🔒
Cheat sheet

Numbers that matter: agile team KPI card

The twelve numbers an agile team runs on: plain definition, formula, where each lives in the workbook and what to do if it moves, with Marcus's SAMPLE baseline and Sprint 6 values.

🔒
Cheat sheet

Tool notes and standards (Correct at November 2026)

Dated notes on the current Scrum and Kanban Guides, Jira, Asana and Trello import, WIP limit and report features, and public-sector agile standards by market, each with the official source.

🔒
Cheat sheet

Scrum and Kanban at a glance

One card with Scrum's accountabilities, events (with timeboxes for one-month and two-week sprints), artifacts and commitments, the Kanban practices and flow measures, and a 'which one?' chooser.

🔒
Cheat sheet

User stories and estimation card (with mistakes to avoid)

The story pattern, INVEST, Given/When/Then criteria, ten splitting patterns, planning poker and counting items, and the twelve most common backlog and estimation mistakes with fixes.

🔒
Import file

Knowledge check: 14 scenario questions (LMS-ready CSV)

14 multiple-choice scenario questions with the correct option and an explanation, for Bodhih LMS or any LMS that imports CSV. Answer key in the briefing plan.

🔒
Calendar plan

Six-sprint plan and 30-day practice calendar

64 calendar events: twelve weekly check-ins, the 30-day practice plan, planning, review and retrospective for six sprints, and four quarterly reviews.

🔒
Import file

Task board: six-sprint plan and 30-day practice (CSV)

56 tasks with milestone, owner, due week or day and status, ready to import into Jira, Asana, Planner or Notion, or to paste into Trello.

🔒
pack

Practice pack: cycle-time calculator, backlog import files and retrospective formats (ZIP)

31 working files: cycle_time.py (cycle time, throughput, WIP, work item age, Monte Carlo forecast), burnup.py, backlog_convert.py and story_lint.py; an 89-item sample export; a 24-row sample backlog with Jira and Asana CSV import files and a Trello paste file; 7 retrospective formats with a facilitation guide; 4 templates; 13 pytest tests. Python 3.9+, no installs.

🔒
Inside the e-book

Chapter by chapter

Each chapter opens with a real situation, gives you a method and ends with something to do today, using the tools in your kit.

Format
PDF e-book + XLSX + fillable PDF + DOCX + printable PDF + ICS + CSV + ZIP practice pack
Files
27 files plus a one-click ZIP
E-book
57 pages
Works with
Excel, Google Sheets, LibreOffice, Word, Google Docs, Acrobat Reader, Outlook, Google Calendar, Jira, Asana, Trello, Python 3.9+, Bodhih LMS and other LMSs
Best for
New Scrum Masters, team leads, Product Owners, non-software managers and students
Spelling
British English with a US glossary; US examples where natural
  1. What agile actually is, and what it is not

    The four values and twelve principles, what the evidence really says, and a 0-4 self-assessment of twelve practices.

  2. Choose Scrum, Kanban or a blend

    Four questions that decide between Scrum, Kanban and Scrum with flow metrics, and how to choose a sprint length.

  3. Roles and accountabilities that work

    One Product Owner, a Scrum Master and Developers: accountabilities, the sponsor's role, team size and a signed charter.

  4. Scrum events, artifacts and their commitments

    Sprint Planning, Daily Scrum, Sprint Review, Retrospective, and the Product Goal, Sprint Goal and Definition of Done.

  5. Kanban and flow: WIP limits, cycle time and Little's Law

    The four flow measures, Little's Law, how to set a WIP limit and a service level expectation, with a Dublin content team.

  6. Writing user stories and acceptance criteria

    The three-part story, INVEST, Given/When/Then criteria, ten ways to split, and a story checker you can run.

  7. Backlog refinement and estimation without the theatre

    Refinement that makes work ready, why estimates go wrong, story points versus counts, and Monte Carlo forecasts.

  8. Sprint planning and the daily scrum

    The three topics of Sprint Planning, capacity planning, a good Sprint Goal and a daily scrum that is not a status meeting.

  9. Sprint reviews and retrospectives that change something

    Reviews as working sessions with users, seven retrospective formats, psychological safety and actions that get done.

  10. Metrics that help: velocity, cycle time, throughput and burn-up

    Velocity used properly, cycle time, throughput, burn-up, the four numbers for leaders and the workbook dashboard.

  11. Agile beyond software, and scaling to many teams

    Kanban and Scrum for non-software teams, public-sector agile standards by market, and when (and whether) to scale.

  12. Tools, AI helpers and your six-sprint adoption plan

    Jira, Asana and Trello set-up and imports, AI helpers with human review, the business case and the six-sprint plan.

What you get

Not just reading. Tools you will actually open again.

Start here

  • The e-book: 12 chapters, about 13,500 words, 35 figures including real screenshots of the kit's tools
  • 00-Start-Here-Agile-Team-Map.pdf: the ten steps, a 15-minute quick start, first hour, first week and the six-sprint plan
  • Situation-Router.pdf: 14 situations and the files to open in order

Workbooks

  • Agile-Team-Master-Workbook.xlsx: 22 sheets including Settings, Self-assessment, Gap plan, Backlog with READY check, Capacity, Sprint log, Flow log, Flow summary, Burn-up, Retro actions, Impediments, Decision log, Readiness check, Dashboard, Tool notes, Crosswalk, RACI, Roadmap, What changed, Glossary and Sources
  • Agile-Adoption-Business-Case-Calculator.xlsx: low, expected, high and do-nothing cases with break-even month and a 24-month chart

Practice pack (ZIP)

  • Agile-Team-Practice-Pack.zip: 31 working files: cycle_time.py (cycle time, throughput, WIP, work item age, Monte Carlo forecast), burnup.py, backlog_convert.py, story_lint.py, an 89-item sample export, a sample backlog with Jira and Asana CSV import files and a Trello paste file, 7 retrospective formats, 4 templates and 13 pytest tests

Fillable PDF forms

  • Team charter and working agreement
  • User story and acceptance criteria worksheet
  • Sprint planning worksheet
  • Sprint review and retrospective record
  • Kanban board design worksheet
  • Readiness check: start Sprint 1 (go / no-go)

Word templates and libraries

  • Leadership sign-off and decision memo
  • Agile ways of working policy (policy starter)
  • Definition of Done and sprint cadence procedure (procedure starter)
  • Message and email library (30 messages)
  • Worked examples: Marcus's filled templates
  • Scenario casebook (9 cases with model answers)
  • AI prompt pack for agile teams (25 prompts)
  • 45-minute team briefing plan and knowledge-check answer key

Cheat sheets

  • Numbers that matter: agile team KPI card
  • Tool notes and standards (Correct at November 2026)
  • Scrum and Kanban at a glance
  • User stories and estimation card (with mistakes to avoid)

Calendar, task board and LMS file

  • Agile-Six-Sprint-Plan-and-30-Day-Practice.ics: 64 events (12 weekly check-ins, the 30-day practice plan, planning, review and retrospective for six sprints, 4 quarterly reviews)
  • Agile-Adoption-Task-Board.csv: 56 tasks for Jira, Asana, Planner or Notion
  • Knowledge-Check-Agile-Scrum-Team.csv: 14 scenario questions for Bodhih LMS or any LMS
Outcomes

When you have worked through it, you will be able to…

Every outcome is practised with a worked example and a tool, not just described.

  • Choose Scrum, Kanban or a blend for your team and record why
  • Write user stories with testable acceptance criteria and check them with a script
  • Plan a sprint from capacity with a Sprint Goal stakeholders understand
  • Set WIP limits and measure cycle time, throughput, WIP and work item age
  • Forecast with a burn-up range and a Monte Carlo forecast instead of a single date
  • Run reviews and retrospectives that produce owned, tracked actions
  • Import a backlog into Jira, Asana or Trello and configure column limits
  • Make a business case and run a go/no-go readiness check before Sprint 1
Measure it

Know your starting point. Prove your progress.

People who measure before and after improve faster and can show it. AssessAll, our sister assessment platform, has AI-graded assessments that pair with this kit. Take one now, work through the kit, then re-take it.

Read a page

A taste of Chapter 8

Before Sprint 2, Marcus filled the workbook's Capacity sheet: for each Developer, working days in the sprint, minus days off, minus a day for events and support, times a focus factor of 80% for interruptions. Mei had two days off; Tom had one. The total came to 48 focused days. With only one sprint of history (23 points), the team chose 30 points in 11 items, with the last four items marked "first to drop". They finished 26 points (87% of the commitment) and met the Sprint Goal. By Sprint 6 the say-do ratio (completed divided by committed points) was 97%, and carry-over had fallen from six items to one.

From The Agile and Scrum Team Kit, Bodhih Training
Why this kit

The honest comparison

Free templates and typical adviceThis kit
Starting pointAdopt the meetings and hopeA measured baseline: cycle time, throughput and WIP from your own export
Method sourceBlog summaries and certification jargonParaphrased from the Scrum Guide, Agile Manifesto and Kanban Guide, cited throughout
Hands-on practiceScreenshots of someone else's boardA practice pack of tested Python tools and sample data you run yourself
Tool set-upGeneric advice that ignores import formatsJira and Asana CSV import files, a Trello paste file and dated tool notes with official links
MetricsVelocity charts used to compare teamsFour numbers for leaders, velocity kept for team planning, forecasts as ranges
RolloutStart Monday and see what happensSign-off memo, business case with a low case, readiness check and a six-sprint calendar
Who it’s for

Made for you if…

  • New Scrum Masters and team leads asked to 'make the team agile'
  • Product Owners and product managers who need a backlog that makes sense
  • Managers of marketing, HR, finance, operations or public-service teams curious about sprints and Kanban
  • Project managers moving from plans and Gantt charts to iterative delivery
  • University students working in project teams or starting jobs where Jira, Asana or Trello is used on day one
Being honest

Probably not for you if…

  • Not a certification course or exam preparation, and no promise of passing any exam
  • Not a guide to large scaling frameworks such as SAFe or LeSS (one chapter explains when and whether to scale)
  • Not legal, HR or procurement advice; templates are starting points to adapt
  • Not affiliated with or endorsed by Atlassian, Asana, Scrum.org, Scrum Inc. or PMI
Why Bodhih

Built by trainers, tested in real rooms.

Bodhih Training has designed and delivered corporate programmes since 2008. Bodhih Pro Kits package what works in those workshops into a guide plus the exact tools we use, so you can apply it the same day without a facilitator in the room.

2008Training organisations since
2,000+Companies served
200,000+Professionals trained
18,000+Programmes delivered
How it works

From here to using it in three steps

  1. STEP 1

    Tap Get the kit

    Name, email and country. UPI, card or netbanking in India; international cards everywhere else. No account to create.

  2. STEP 2

    Download instantly

    Your download page opens at once, with every file and a one-click ZIP. A permanent link lands in your inbox too.

  3. STEP 3

    Open the first tool

    Start with the quick-start chapter, then the main spreadsheet or planner. Most buyers use something from the kit the same day.

Ready when you are

Start less, finish more, from this week

Open the Start-here map, run the 15-minute quick start and see your team's real flow for the first time. Whether you begin with the self-assessment tonight or the charter session next week, the next step is already in the kit.

$29one-time payment

Personal licence for the buyer's own use, including use with your own team where the kit says so. Please don't share or resell the files. Team and company licences: solutions@bodhih.com.

What buyers say

No ratings yet. Only people who have bought this kit can rate it - every buyer gets a one-click rating link a couple of days after their purchase.

Questions buyers ask

The Agile and Scrum Team Kit: FAQs

Read the free guideAlready bought? Resend my link

What is the difference between agile, Scrum and Kanban?

Agile is the set of values and principles in the 2001 Agile Manifesto. Scrum is a lightweight framework built on fixed-length sprints, three accountabilities and a few events. Kanban manages the flow of work with a visible board, limits on work in progress and four flow measures. Many teams blend Scrum's rhythm with Kanban's flow measures, which is this kit's default.

Should my team use Scrum or Kanban?

Use Scrum when most work serves one product goal and stakeholders want to see results regularly. Use Kanban when work arrives continuously in different types with same-day urgency. If work in progress is high, add WIP limits and flow measures either way. Chapter 2 and the Scrum and Kanban at a glance card walk you through four questions.

Does this kit work for non-software teams such as marketing, HR or finance?

Yes. The method and templates include non-software versions: a Definition of Done for content and operations work, a Kanban board design worksheet and casebook cases for a content team, an HR team and a student group. Keep personal data off boards; the kit shows how.

Will this help me pass a Scrum or agile certification exam?

It will help you understand Scrum and Kanban in practice, but it is not exam preparation and does not promise any result. Read the official Scrum Guide and your exam body's syllabus as well. To check your judgement, AssessAll's Project and Delivery Leadership assessment is a separate option.

How long does it take to set up?

The quick start takes 15 minutes. A first useful hour gets your baseline numbers and self-assessment. The kit's plan assumes two weeks of preparation and then six two-week sprints, with a calendar file and task board for every step.

Do I need to know Python to use the practice pack?

No. You run each tool with one command that the book shows, and the book shows the output you should see. Python 3.9 or newer is enough; nothing else to install. The workbook does the same arithmetic if you prefer spreadsheets.

Can I import the sample backlog into Jira, Asana or Trello?

Yes. The pack includes a Jira CSV that keeps epics and stories linked, an Asana CSV in the column order Asana documents, and a Trello paste file, because Trello has no generic CSV importer. The Tool notes sheet links each vendor's official help page with the date it was checked.

How do I measure whether agile is working?

Capture a baseline before you change anything, then track four numbers each sprint: a burn-up forecast range, median cycle time, Sprint Goals met and escaped defects. The cycle-time calculator and the workbook dashboard do the arithmetic. Velocity stays inside the team.

Is it wrong to compare velocity between teams?

Yes. Story points are each team's own relative scale, so comparing them compares different rulers and invites inflated estimates. Compare cycle time, throughput and goals met instead. The policy starter and message library include wording for that conversation.

Is agile required by law in the US, UK, Canada, the EU, Australia or New Zealand?

No law requires a private company to use Scrum or Kanban. Public bodies in these markets publish digital service standards that ask for agile, iterative delivery. The Crosswalk sheet lists each with its official source, correct at November 2026.

Can I use these files with my team?

Yes, within your own organisation under the personal licence. For company-wide or multi-team licences, email solutions@bodhih.com. For habits that stick after the training, Jobulary's guide to if-then plans is a useful companion read.

How much does The Agile and Scrum Team Kit cost?

₹999 including 18% GST for buyers in India, or $29 for buyers outside India. One-time payment, no subscription, with an automatic invoice.

How do I get the files after paying?

Instantly. Your download page opens the moment payment succeeds, and a permanent download link is emailed to you. Download each file separately or everything in one ZIP.

What software do I need?

Any of the usual tools: Excel or Google Sheets for spreadsheets, Word or Google Docs for templates, Adobe Acrobat Reader, Preview, Xodo or GoodNotes for the fillable PDFs, and Google, Outlook or Apple Calendar for the calendar plan.

Can I get a refund?

Because it is a digital download, kits are not refundable once downloaded. We always refund a duplicate charge or a failed delivery, and if a file is corrupted and we cannot fix it within 3 working days. Full terms: bodhih.org/refunds.

Can my company buy this for a team?

Yes. Team and company licences, and workshops on this topic run by Bodhih Training, are available. Write to solutions@bodhih.com or call +91 99000 11601.

$29