Skip to main content

Conceptual Models and Estimation: A Process

In my last entry, I introduced the notion of using conceptual models to estimate the cost and duration of a software project. In this entry, I outline a process for doing so.
  1. Compose a conceptual model of the system. Typically, most of the nouns mentioned in use cases appear in the conceptual model.
  2. Identify concept clusters. A concept cluster is a group of related concepts. Groups of concepts that have many associations among them are good candidates. Concept clusters roughly correspond to the components of the system assignable to different teams of developers.
  3. Count the number of concepts in each concept cluster. The number of concepts in a cluster is roughly proportional to the level of effort required to implement the corresponding component of the system.
  4. Assign a concept multiplier to each cluster. A concept multiplier represents the number of man-hours it will take to implement the functionality related to a single concept. In some cases, the multiplier for the concepts in one cluster will differ from the muliplier for concepts in other clusters. This step requires close consultation among product management, architects, and developers to determine the most realistic multiplier.
  5. Compute total man-hours. The total man-hours is equal to the summation of the products of the number of concepts in each cluster and the concept multiplier for that cluster.

After estimating the project using this object-oriented method, you can compare the results to estimates based on a functional estimation method.

Comments

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio