Tomorrow night I’m speaking at the BBC Cardiff Kanban Meet Up on the topic of “Delivering incrementally with Agile methods”.
I’ll be presenting material from three of my blog posts:
Come along if you are in the area.
I’ve managed to publish four pasts each month since June. (Pats self on back.) With that volume of material coming out I’ve decided to put a bit of structure around what gets published when.
So here is my current thinking on a monthly publication schedule …
Last year I wrote a series of blog posts for the Project Research Institute of Athabascau University in Canada. As I mentioned before the PMI’s aim was to introduce their relatively mainstream audience to an Agile perspective. My aim was to show how the principles and practices of Lean-Agile Software Development offer creative solutions to general project challenges.
The PMI has now published all of my posts, including:
- Why Lean-Agile is relevant to all Project Managers
- A Lean-Agile Perspective on Project Governance
- Managing Complexity with Agility
- Empirical Project Management: Agile estimation and being “Done”
- Agile Experiments in Self-Organization
Apologies for the recent outage. My hosting provider scheduled an upgrade to the server and broke the site at the same time. Normal service has resumed.
I was recently asked to write a series of blog posts for the Project Research Institute of Athabascau University in Canada. The institute wanted to expose their audience, mainstream project managers, to an Agile perspective. I relished the opportunity and readily agreed.
My aim with my PMI series is to show how the principles and practices of Lean-Agile Software Development offer creative solutions to general project challenges such as governance, uncertainty and complexity, under estimation and empowerment. My first post for the institute tackles this head on and I argue that Lean-Agile relevant to all project managers” simply because Lean-Agile offers a new slant on these problems. I am not advocating the wholesale adoption of Agile by all project managers. Merely to offer up a different perspective to that of main stream project management. Armed with this perspective project managers from other domains may be better placed to face their own challenges.
The first couple of posts have already been published and the rest of the series will appear over the next couple of months. If you want to follow the series on the PIR site then have a look at my blog at Athabascau. Otherwise I’ll also post updates here.
I have moved the website and blog from Joomla to WordPress. WordPress is simpler, with a cleaner user interface, yet has better functionality out-of-the-box. Apologies if anybody has any bookmarks which are now broken.
Kelley Hunsberger interviewed me for her article “Change is Good: For agile projects, redefining scope isn’t such a creepy thing”. It is great to see agile thinking in a mainstream project management magazine such as PM Network. And the article was a very nice little summary of why it is good to embrace change.
I took the opportunity to reiterate some of the points I’ve already made on Agile Project Scope and Agile Change Management, namely that all projects experience changing requirements and it is better to embrace this than fight it. For example legitimate sources of change include:
- The customer learns as they see working functionality emerging of the development effort.
- The technical team is also learning as they discover what works.
- The environmental context might also dictate changes, such as changes in the market or legislation.
Ignoring any of these sources of “scope creep” would be foolish.