Quantum Mechanics, Buddhism, and Projects - Again!

Today I'm proud to announce that my QMBP :-) article was again published by a major web site on business analysis, requirements engineering and product management: The Requirements Network. The site is full of interesting material for beginners and experts. I recommend reading it.

You'll find the piece of mine and some interesting comments here.

And - ha! - mind the URL of my article: ... node/1874.

Did you know that Winston Churchill was born that year? Must say something ... :-D

Find out more about 1874.

Use Case Content Patterns Updated

Martin Langlands incorporated "my" DESTRUCTOR pattern into one article, now version 2 of his Use Case Content Patterns description. Have a look here, the whole thing is easier to handle now.

Hint: Click 'files' at the bottom of the wiki page to see the pattern file. Sorry for the inconvenience!

Update on the Credibility-Info for Estimations

I updated this post with a few more interesting quotes and most of all the beautiful idea of giving ranges backwards, like "the project will be finished in 6-4 months", as the first number of a range seems to stick in people's minds.

A year ago in August on Clear Conceptual Thinking

Use cases

• Describing Alternate Courses of Action in Use Cases
  

Agile

• Communicating Plans in Agile Development
• 12 Tough Questions for Waterfall Projects
  

Other Stuff

• Humane Interface Design
• Doing Job Interviews Efficiently
  

Update on Finding the right cycle time

I updated

Finding the right cycle time

with the idea of 1-day iterations. Thanks to Mishkin Berteig for injecting this idea.
For those of you who think 1-week iterations are ridiculous, and 1-day iterations can't reasonably be a serious contribution of mine, think again.

Update on Being Agile on Offshore Projects

I updated

Being Agile on Offshore Projects,

with some information advocating NOT to do offshoring. Research shows that team productivity could be doubled if the team is in one room. While this seems like an argument often heard, the point is that there's proof.

Why Managing Too Many Risks is Too Risky

I wrote a guest post over at the Raven's Brain weblog. The topic is 'Heaps of Risks - Why Managing Too Many Risks is Too Risky'.

Risk management is a source of unusual human behavior: euphoria or excessive gambling when risk is underestimated, and panic attacks or depression when we predict that things are riskier than they really are. Both are risks by themselves.
In the post I'll address a risk that is also closely related to human behavior and presents a risk: Overly extensive risk registers, i.e. a list of several dozends of risks for a given project.

Read more

If it feels too troublesome to leave a comment there, why not leave it here?

A year ago in May on Clear Conceptual Thinking

Use cases

• Prioritizing Use Cases
• Finding the right size for a use case
• Naming Use Cases

Stuff

• Finding key Stakeholders
• Principles of Modelling Static OO-Models
• BUFR (big up-front requirements)
• User-Centered Development / Personas
• How to Determine if a Requirement is Atomic
• Change and Software are Twins
• Effort Needed for Product Enhancements
• Testcase Numbers based on Function Points

Calculate / Measure

• Calculating Success
• Estimating ROI
• Changing Requirements with Fixed Price Contracts

Citations

• Hume on Ambiguity
• Eisenhower on Plans

A Year Ago in April on Clear Conceptual Thinking

Stuff:

• Avoid Requirements Related Defects in IT-Systems
  
• Non-functional Requirements and Levels of Specification
  
• Signs and Symbols
  
• Principles for Requirements Engineering Tasks
  

The Series about Tenders

• Evaluate the Tenders
  
• Evaluate the Presentations
  
• Send The Call for Tenders
  
• Prepare Call for Tenders
  
• Call for Tenders
  

About

• About Me
  
• About This Blog
  

More Stuff:

• Lean Product Management
  
• RE-Prinzipien (german)
  
• Principles of Clear Thinking
  
• General Rules for Prioritizing Tasks in Evolutionary Development
  

Quantum Mechanics, Buddhism, and Projects

I'm pleased to announce a guest post I wrote over at the pm411.org Project Management Podcast / Weblog. Ron Holohan was broad-minded enough to let me share my thoughts on the holy project trinity (Time, Budget, Scope). In essence, it's about Quantum Mechanics, Buddhism, and Projects. 

Get over there if you like to read about my more fluffy thoughts. Thank you!

Update on the Evaluation of Tenders

Today, I updated the Rules for the Evaluation of Tenders with thoughts on how to check references.
Have a look.

There's also a category for all the blog posts concerning tenders.