The first step in writing the use cases for a project is to define the scope of the project. One way to do that is to list the use case names that define all of the user goals that are in scope. To do that, you need to know how to write good use case names. Good use case names also serve as a great reference and provide context and understanding throughout the life of the project. We present our tips for writing good use case names.
Flashback
Posted on:
Flashback: A Year Ago This Week on Tyner Blain [2006-01-20]
A look back at the best from a year ago…
Requirements / Requirements Models / Use Cases
Posted on:
Informal Use Case Template
Free Microsoft Word 2003 template for creating informal use cases. This template is built as a form with guiding text and help text. Read how to use it and download it today.
Foundation series / Product Management
Posted on:
Foundation Series: Inbound and Outbound Product Management
Inbound product manager or outbound product manager – what’s the difference? We’ll look at the overall role, and the breakdown of responsibilities. We also follow-up with some suggested detailed reading.
Slightly off-topic
Posted on:
Five Things You Don’t Know About Me
For folks who don’t read a lot of blogs – there’s a meme going on right now where people list five things that most people don’t know about them. This spreads virally, like the old email chain letters. After you share your five things, you tag five more people. Read on to see my five things…
Product Management
Posted on:
Product Manager Staffing Levels – More Survey Results
One of our readers is working on determining product manager staffing levels for her company. While every company is different, it always helps to understand where our peers are. We do some in-depth analysis of the 2006 Pragmatic Marketing product management and marketing survey to see how other companies set their staffing levels.
Lists / Marketing
Posted on:
Marketing Truths – Don’t Tell the Developers
Marketing is as foreign to most software developers as swimming is to fish. We’ve found a list of ten truths of marketing, and we’re secretly sharing them with the developers who hang out here. Shhh. Don’t tell anyone in marketing.
Flashback
Posted on:
Flashback: A Year Ago This Week on Tyner Blain [2006-01-13]
A look back at the best from a year ago
Agile / Process Improvement / Software development
Posted on:
Code Debt: Neither A Borrower…
Code Debt is the debt we incur when we write sloppy code. We might do this to rush something out the door, with the plan to refactor later. Agile methodologies focus on delivering functionality quickly. They also invoke a mantra of refactoring – “make it better next release.” This can create pressure to “get it done” that overwhelms the objective of “get it done right.” Taking on code debt like this is about as smart as using one credit card to pay off another one.