As I was writing a BLOG entry I saw a new version of the blogging software was available. Being somewhat of a geek myself I went to look at the change list. I wanted to see if some of the things that drive me crazy have been fixed. At the bottom of the page I saw the phrase "code is poetry" Having a background in software development this comment put a smile on my face. I have worked with all types of developers. Some say "if it is working it is good, don't change it" While there is some truth …
Measurement certainly requires looking to the past to learn of the future. But there is a huge amount to be learned from the lessons learned themselves. Looking back on the SEER for IT development there are several lessons learned that go beyond just the measurements.…
As I read my friend Paul Glen's IT professionalism email today (well worth signing up for) I was struck by his analogy of the California wildfires and IT. He pointed out that many of the problems firefighters faced were due to persons who refused to evacuate when told to. He then discussed how this impacts IT. For example... items such as those who hook up their own wireless routers or use different cell phones than those certified by the company. Then expecting support for their unique configuration.
Quantifying those costs with a quick trade in SEER for IT (SEER-IT) showed:…
I was speaking with Ton Dekker and others from Galorath this morning abut the ROI from viable estimation. Ton pointed to the empirical evidence of a 10 to 15% saving in overall IT spending based on the implementation of a metrics program and estimation going along with it. Ton also spoke of MOUSE.... the "list of activities and services that need to be carried out to get a metrics program up and running." The activity and service groups within MOUSE include:
An article in the Wall Street Journal discussed studies measuring productivity of common management techniques such as setting targets, monitoring performance and lean manufacturing and were able to quantify the revenue and cost improvements associated with them.
It is good to see measurement and analysis playing such an important role in manufacturing operations.
the study found US factories are better managed than other countries but the gap is shrinking.
- Challenging the state of-the-art
- Shortages of talent, especially in early project months
- Imposition of unrealistic schedules
- Underfunding, either intentional or due to inadequate estimating
- Poor definition of requirements
- Customer uncertainty about what they want
I recently got the clever idea to purchase a folding bicycle so I could have a decent bike when on vacation... The plan was to check the bicycle with the airlines in a standard suitcase. I spent hours researching on the web. I spoke to a couple of bike stores. Then I placed my order. A few days later a BIG box appeared on my doorstep. The bicycle was a magnificent piece of engineering. Unfolds in about 15 seconds. Only one problem. The bicycle was designed for the older airline luggage size. With the newer, more stringent standards this bicycle …
There is a great BLOG entry from someone who went back to Microsoft after a year at Google. Some of his observations are very relevant to the use of open source software. He points out that at Google there is little of project management or testing.
"On the other hand, I was using Google software... there's just too much of it that is regularly broken. It seems like every week 10% of all the features are broken in one or the other browser. And it's a different 10% every week - the old bugs are getting fixed, the new …
I was at the SCEA (Society of Cost Estimation and Analysis) conference this week. Some of the buzz was about risk, both talks given at the conference and the ongoing risk arguments. For several years the risk gurus have been lining up to show how to do more robust risk analysis. While I would not say they are getting carried away I would say i get concerned with the differences of opinion and the numerous options provided by smart people.
One of my heroes in risk, Dr. Steve Book or MCR points out that risk analysis should include correlation.
Our SEER for Manufacturing (formally SEER-DFM) and now abbreviated SEER-MFG, uses what we call bottoms up parametrics.. Bottoms up parametrics differ from general parametric estimation modeling in a few respects:
- Bottoms Up Parametrics Don't Necessarily Minimize the Number of Inputs
- Bottoms Up Parametrics ask for detailed levels that traditional parametric estimating would not.
I was briefed on a new tooling analysis method that actually allows the user to specify specific tools if they want to. Way more detail than a traditional parametric model. But exactly what the bottoms up people desire.…