The Improving Projects blog from Huge IO (UK & Ireland) is primarily about products, organisations and projects... and how to improve them. As well as musings on agile processes, software engineering in general, and methods like Kanban and Scrum, there's advice here too for users of process planning, execution and improvement tools - and the metrics they can provide. https://uk.huge.io
If you have collaborating teams of professionals that need to …plan, execute and monitor projects;define and improve their processes in terms of the tasks and documents that make up typical projects (and yet not be constrained by a “process straight-jacket”);control projects by prioritizing requirements, varying resources and defining target dates;bring together all the plans, resources and documents for their projects in one versioned and auditable repository; …then considering process improvement through xProcess is an obvious next step. As we get closer to the release of version 2.0 of the product, one way to get a really close view of the new features that this version will bring is to participate in the beta programme now under way. Note that the beta programme will continue after the 2.0 release, allowing participants to see the very latest features coming through into the product.
If you think this programme might be for you, do let me know.
I'm amazed by how many people I meet that tell me their project, or projects in their organisation, use some kind of variant of the waterfall lifecycle. It happened to me again today while conversing with a friend who works for one of the major international banks. The waterfall is as ubiquitous as death, taxes and project overruns!
[And now I discover there's an unmissable conference on the subject - stop reading this blog and go now to waterfall2006.com! But more on this later.]
The interesting thing about the waterfall lifecycle is that it has very few proponents among the luminaries of the industry. Even Winston Royce, who is usually credited with inventing the waterfall in his 1970 paper to the IEEE was actually criticising the approach of trying to deliver a complete system in one iteration. While I'm in name-dropping mode, I could mention that I met Winston when he was working at TRW. He had a most distinguished pedigree in software engineering but he was hardly the u…
Occasionally I get asked questions that force me to re-consider my elevator-pitch for xProcess. So somebody just asked me why he should use xProcess with his development teams. Here's my reply:
"xProcess merges a continual process improvement capability (dynamic process management) with fully connected project collaboration and management (dynamic project execution). "If you capture your processes in xProcess it means that the patterns of tasks, deliverables, quality criteria and workflows in the process can be realized by project managers and participants as actual elements in running projects. (Since all data in xProcess is fully versioned you also have a full audit trail of who changed what, when and even in some cases why.) This means it is much easier for people to be compliant with your corporate processes than not to be! Given the investment you are making in process improvement this is great news. However xProcess is not a straight-jacket. If project managers choo…