As a project manager, one of the common challenges in your day-to-day work is having to extract timely and insightful status updates from engineers. In my experiences, one-on-one or in daily standups engineers are very capable of explaining their current project trajectory provided you probe and question right, but having them put it on Jira … Continue reading Get Rid of Daily Standups and to Get Engineers to Update You Daily
What is a User Acceptance Criteria? User Acceptance Criteria or UAC, is the contract between the product owner and scrum team, letting them know what needs to be done functionality wise, in order to meet the user’s need and exit successfully. A set of explicit and exhaustive conditions, that detail comprehensively the scope of the … Continue reading Reasons Why you Need a Good Acceptance Criteria
Something many PMBOK practitioners are familiar with already, but always worth honing in on, is the project or program ritual of formalizing a project charter. A project charter is the pinnacle of any project, it is the justification and mandate for kicking off a project. Most commonly prepared at the start of a project by … Continue reading Formalizing a Project Charter
Most practitioners associate the tenets of the agile manifesto as the guiding principles in executing their scrum agendas. In this article, With the premise of Scrum optimized on empirical process control, I wanted to spend some time looking into the three pillars of Scrum theory: transparency, inspection and adaption and provide some annotation on what they really mean, and why these pillars should be the foundations of your practice.
Something as a practicing program manager I tend to always use as tenets when guiding teams, is relying on the spiritual bible of contemporary project management, and that’s the Agile Manifesto. Products of the Agile Alliance, the premise of the Manifesto is to simplify the practice of project management through a lightweight framework to build software expeditiously with bias for customer validation over processes and documentation and red tape.
The two drivers behind the manifesto are iterative and incremental development, over pre-medicated and over planning, and creating higher quality software in shorter time, or more concisely, build more with less.