Skip to main content

Let me invite you to the Brewery!

Working on the principle that even I could organize an event in a brewery, we've decided the launch party for xProcess 2 should be at the old Whitbread Brewery in the City of London (see www.thebrewery.co.uk for more details of the venue). It's an historic old building and, in the hope that there could be something good stored down there, we're meeting in the Smeeton Vaults.

If you're in striking distance of the City I very much hope you'll join us for the event. Here are the details:

Date: Monday 24th April
Registration and coffee: 3pm
Programme:
3.30pm – 5pm followed by drinks reception and exhibition
Venue: The Brewery , Chiswell Street, London EC1Y 4SD
Underground: 3 minutes walk from Moorgate or Barbican; 10 minutes walk from Liverpool Street or Bank.

Come and hear about ground-breaking developments in xProcess for capturing and improving the processes behind your projects, and then supporting your whole team in estimating, planning, resourcing, scheduling and monitoring the live projects. Simple to install, xProcess gives the team access to all project artifacts and the latest process and scheduling data. Information from the team and other stakeholders concerning estimates, availability, priorities and risk is available to all other stakeholders, and every change is versioned and auditable. Find out how xProcess can empower your teams and increase agility, best practice conformance, visibility of plans and progress, auditability and quality.

Register for the event now at www.ivis.com/london-launch or call Laura on 023 8087 5899.

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…