Published in


No-Code Project Management

No Code Projects do not give you an excuse to abandon project management

Photo by Team Xperian on Unsplash

No-Code Scrum?

  1. Define simple Solution or Product Features using User Stories and Epics, and I also recommend at least simple Use Cases (more discussion on this below).
  2. Features get added to the Solution (or Product) Backlog.
  3. Sprints are Planned and Feature Implementation estimated as Features are added to the Sprint Backlog.
  4. Sprints are Executed and Sprint Reviews are conducted.
  5. And Features are Implemented and deployed to the current version.

Use Cases to the Rescue

No Code, but Good Project Management Still Required



Brutally honest thinking and commentary about managing (and sometimes even just surviving) Projects edited by Peter Walzer, Principal of Blue Globe Management Consulting (a division of Blue Globe Group, Inc.,

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Peter Walzer

Peter Walzer has over 30 years of experience in management consulting, project management, systems development, and “get up you’re not hurt” persistence.