Home »
Posts tagged "Requirements" (Page 2)
The problem is not a surprise request for a quick estimate. The problem is that we are not prepared to give quick estimates. Here is how we did it.
Continue reading »
January 11, 2013 Bruce Benson
Planning
Establish up front how we are going to know if the agile adoption was successful? If we have to do that, we may have other problems to deal with first.
Continue reading »
April 13, 2012 Bruce Benson
Change Management, Metrics
Some key project metrics not only provide tactical insight into how a project is going, they can also provide an overall strategic view not found elsewhere. Here are three we've used successfully.
Continue reading »
November 21, 2011 Bruce Benson
Metrics
1 Comment
The commercial world is all about making money. Yet successful companies often have a noble mission beyond just making money that helps drive their success.
Continue reading »
November 18, 2011 Bruce Benson
Leadership
We took the official plan document and turned it into a real plan that we used everyday. This was different from the classic plan that was created to meet a checklist requirement. Here is how we made the change and how moving to a real plan can often confuse folks and how we overcame this normal confusion.
Continue reading »
October 12, 2011 Bruce Benson
Planning
Especially for complex and costly IT projects, customers need to invest more in the up-front evaluation. Oh, no. Here we go again.
Continue reading »
August 11, 2011 Bruce Benson
Planning
I'm a great advocate of managing using objective, data driven, project management tools. I often call it being "brutally honest" but with the insight it is only "brutal" to organizations that have locked themselves into other than objective approaches. Here are five reasons why being objective is hard, and ways we successfully overcame these barriers.
Continue reading »
February 22, 2011 Bruce Benson
Metrics
Sometimes it is the team process and not the project requirements that determines a project's schedule.
Continue reading »
February 15, 2011 Bruce Benson
Planning
7 Comments
It happened pretty regularly. To make some functionally work on the project we needed something else that we overlooked. No problem. We make the change -- tag it as a missed requirement in our project management tool -- and approve it. A couple of weeks later the additional functionality is completed and gets submitted to be put into the product. It is submitted as a “new requirement.” It shows up as scope creep. I called up the project manager and explain they tagged it incorrectly. Please change it to a missed requirement. “Oh no!”, she practically yells, “It is a new requirement!
Continue reading »
October 19, 2010 Bruce Benson
Metrics
I had a job interview for VP of Development. The interviewing VP with a long history in the industry asked me a simple question: Did I think software development was a repeatable process? I said yes. I won't describe the ensuing discussion except to say I didn't get the job. We didn't even get to talk about project management tools!
Continue reading »
August 23, 2010 Bruce Benson
Planning