Archive for January, 2007

Just Plain BadLameAverageGoodGreat (12 votes, average: 4.17 out of 5)
Loading ... Loading ...
January 19th, 2007

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.

Just Plain BadLameAverageGoodGreat (3 votes, average: 4.67 out of 5)
Loading ... Loading ...
January 18th, 2007

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.

Just Plain BadLameAverageGoodGreat (3 votes, average: 3 out of 5)
Loading ... Loading ...
January 17th, 2007

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…

Just Plain BadLameAverageGoodGreat (7 votes, average: 4 out of 5)
Loading ... Loading ...
January 16th, 2007

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.

Just Plain BadLameAverageGoodGreat (7 votes, average: 4 out of 5)
Loading ... Loading ...
January 15th, 2007

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.

Just Plain BadLameAverageGoodGreat (1 votes, average: 5 out of 5)
Loading ... Loading ...
January 13th, 2007

Flashback: A Year Ago This Week on Tyner Blain [2006-01-13]

A look back at the best from a year ago

Just Plain BadLameAverageGoodGreat (5 votes, average: 4.6 out of 5)
Loading ... Loading ...
January 12th, 2007

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.

Just Plain BadLameAverageGoodGreat (3 votes, average: 4.33 out of 5)
Loading ... Loading ...
January 11th, 2007

The Wisdom of Crowds Prevents People’s Passions

The wisdom of crowds helps us avoid stupid decisions. Unfortunately, it also prevents innovative, passionate, fantastic decisions. Collective Intelligence is collective insipidness. We need to keep the inputs of individuals in the mix.

Just Plain BadLameAverageGoodGreat (3 votes, average: 4.67 out of 5)
Loading ... Loading ...
January 10th, 2007

Usability Sells Software - Word of Mouth Marketing

There are three main models for selling software. You can hire a direct sales force. You can spend a lot on marketing and advertising. You can let your users sell the software for you, a technique commonly known as viral marketing. There’s a catch with viral marketing - users have to like your software.

Just Plain BadLameAverageGoodGreat (3 votes, average: 3.67 out of 5)
Loading ... Loading ...
January 9th, 2007

Why Requirements Approval Matters and How To Make It Easier

Getting requirements documents approved can be a pain in the butt. Why do we need to do it in the first place? The approval process is more than just reaching concensus or creating a contract. Done correctly, it presents an opportunity to get more inputs from stakeholders.