Programme vs. Project Initiation
Sequel: The Caffeine Chronicles - Starring the Pigeon Dynasty
In a world where coffee is currency, and pigeons have strong opinions about your agile workflow...
In a world where coffee is currency, and pigeons have strong opinions about your agile workflow...
If you’ve ever wondered why project managers resemble overcaffeinated squirrels while programme managers look like they have mastered the art of herding cats while riding a unicycle, let’s demystify these roles.
While the overall planning of project timeline gets lot of attention in the world of software, the most important aspect of project management in my experience is maintaining and tracking Issues and Actions. This in normal project management practice is carried out through the use of an Actions Log
and an Issues Log
. In addition any medium complexity project invariably will have internal and external dependencies / constraints, risks which I tend to track on Constraints Log
and Risks Log
. Finally, every project has decisions that I track on a Decisions Log
.
Additionally, any opportunities that I identify during the course of project that are not in the scope of my project I capture those too in an Opportunities Log
Now all these logs have fairly standard fields so I created and started using an excel template and began calling it CARDIO Log
short for log of Constraints, Actions, Risks, Decisions, Issues, Opportunities for a given project. This has worked well for me over the past 15 years or so but there are times where in order to maintain it meant cross linking an action to an issue or a risk and so on and more often than not it would become easier to just track actions in one of the other logs and that would make it a bit chaotic.
That problem, however, is what I thought, can be resolved using Logseq especially after starting with the template by the Logseq community user Luhman and starting with his template and explanation provided here.