Skip to main content

Who needs what?

One of the key ideas in xProcess is that it puts planning and process control in everyone’s hands - at the level they need it. For example...

Project Participants can:
  • see their tasks and priorities (potentially across multiple projects)
  • update estimates and progress
  • update their availability and overhead activities
  • update their active tasks and close their tasks when complete
  • see changes to priorities and target dates

Project Managers and Planners can:
  • create project tasks and prioritize them
  • change available resources for the project and assign them to roles or tasks
  • set the scope and target dates for timeboxes and releases
  • see immediately if tasks are forecast to miss targets and why
  • view burndown or Gantt charts of the whole project or timeboxes
  • select and/or customize the processes their projects use

Project Executives and Stakeholders can:
  • overview the goals and progress of multiple projects
  • monitor and improve the processes adopted by projects
  • compare and contrast processes if they are different
  • examine “what-if” scenarios by varying resource deployment
  • redeploy resources between projects
  • monitor financials spend and earned value of projects
  • generate different format reports for projects and resources.

Process Improvement Managers can:
  • monitor and compare the progress of projects applying different processes
  • capture process improvement strategies from different projects
  • define and improve company standard processes
  • monitor process and quality compliance.

The new UI in version 2.5 will reflect the different emphasis required by different roles with tailored perspectives for Project Managers, Project Participants and Process Definers. Expect this to be developed further in future releases.
Post a Comment

Popular posts from this blog

Does your Definition of Done allow known defects?

Is it just me or do you also find it odd that some teams have clauses like this in their definition of done (DoD)?
... the Story will contain defects of level 3 severity or less only ... Of course they don't mean you have to put minor bugs in your code - that really would be mad - but it does mean you can sign the Story off as "Done"if the bugs you discover in it are only minor (like spelling mistakes, graphical misalignment, faults with easy workarounds, etc.). I saw DoDs like this some time ago and was seriously puzzled by the madness of it. I was reminded of it again at a meet-up discussion recently - it's clearly a practice that's not uncommon.

Let's look at the consequences of this policy. 

Potentially for every User Story that is signed off as "Done" there could be several additional Defect Stories (of low priority) that will be created. It's possible that finishing a Story (with no additional user requirements) will result in an increase in…

"Plan of Intent" and "Plan of Record"

Ron Lichty is well known in the Software Engineering community on the West Coast as a practitioner, as a seasoned project manager of many successful ventures and in a number of SIGs and conferences in which he is active. In spite of knowing Ron by correspondence over a long period of time it was only at JavaOne this year that we finally got together and I'm very glad we did.

Ron wrote to me after our meeting:

I told a number of people later at JavaOne, and even later that evening at the Software Engineering Management SIG, about xProcess. It really looks good. A question came up: It's a common technique in large organizations to keep a "Plan of Intent" and a "Plan of Record" - to have two project plans, one for the business partners and boss, one you actually execute to. Any support for that in xProcess?

Good question! Here's my reply...

There is support in xProcess for an arbitrary number of target levels through what we call (in the process definitions) P…

Understanding Cost of Delay and its Use in Kanban

Cost of Delay (CoD) is a vital concept to understand in product development. It should be a guide to the ordering of work items, even if - as is often the case - estimating it quantitatively may be difficult or even impossible. Analysing Cost of Delay (even if done qualitatively) is important because it focuses on the business value of work items and how that value changes over time. An understanding of Cost of Delay is essential if you want to maximise the flow of value to your customers.

Don Reinertsen in his book Flow [1] has shown that, if you want to deliver the maximum business value with a given size team, you give the highest priority, not to the most valuable work items in your "pool of ideas," not even to the most urgent items (those whose business value decays at the fastest rate), nor to your smallest items. Rather you should prioritise those items with the highest value of urgency (or CoD) divided by the time taken to implement them. Reinertsen called this appro…