Skip to main content

ScrumMD

Logo

ScrumMD started with a question: What if we could have a scrum board driven entirely by md files and the CLI, and use it with git?

I know that it's going to be of niche use, but it opens up a number of great ways to do the scrum process. For instance:

  • You can run standup for sprint1 with:
vim `sbl -b sprint1`
  • You can manage your cards with git...
  • ... and can add them in the repository that they are for
  • It's all text - so integrate with whatever you want

The very basics are that you have a scrum folder, and you can put cards inside it. A card is very simple - it's just a markdown file with at least a summary field. For instance -

---
Summary: Make the thing
---

# Description

Take the steps to make the thing

# Dependencies

-   [[thing02]]
-   [[thing03]]

would be a completely valid card that can be explored with ScrumMD. But - per the documentation - it does a bunch more!

There's also some funky other tools like sboard that let you view a visual representation of the Scrum board in the console - for instance:

$ sboard --group-by status
|not fully defined  |ready              |in progress        |in testing         |done               |None               |
|-------------------|-------------------|-------------------|-------------------|-------------------|-------------------|
|cli008             |cli028             |cli034             |                   |cli018             |v0-1               |
|Permit newlines in…|Allow underline he…|Show scrum board o…|                   |`sbl` Group By     |Items remaining to…|
|                   |                   |                   |                   |                   |                   |
|cli029             |cli032             |                   |                   |cli019             |                   |
|Allow subheadings …|Write access to pr…|                   |                   |String property af…|                   |
|                   |                   |                   |                   |                   |                   |

Documentation

Find it all over on Read The Docs. There's a fair bit of detail, and a tutorial for getting started.

License

This is published under the GNU General Public License v3.0. I am willing to discuss making it available under another license, or providing pai

Metadata

Release files for scrummd 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for scrummd 0.2.0
File Size Uploaded
scrummd-0.2.0.tar.gz 584.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for scrummd 0.2.0
File Interpreter ABI Platform
scrummd-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 1.2 MB

Release files / scrummd-0.2.0.tar.gz

Download URL scrummd-0.2.0.tar.gz
Size 584.7 kB
Tags Source
SHA-256 checksum
How to use checksums
8a8c966b0d37a6fe751a7efac56bdba6bbb327a479cf8fc13463232fb05faa7a
BLAKE2b-256 checksum
How to use checksums
d3bd240a9da631043ddda36e8bdd0fbb81e042631de9c3b47752076a680e2721
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2025.

Transparency log

Release files / scrummd-0.2.0-py3-none-any.whl

Download URL scrummd-0.2.0-py3-none-any.whl
Size 586.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7a19449e0bef76570a14914fd35bb34fa19818a885a193881cca75c99f5a2585
BLAKE2b-256 checksum
How to use checksums
14f51832adb9f09b4e0d861d524c71020609c6a68c6b70c856e50b05dfbf73e8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.0 This release

2 release files

0.1.2

2 release files

0.1.0

2 release files

0.0.15

2 release files

0.0.14

2 release files

0.0.8

2 release files

0.0.5

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page