Welcome to product management! Over the the better part of three months, Adrienne Tan at brainmates, product management people, put together a series of posts with ten tips for new product managers. Check out our article for a quick summary, and links to all the articles at brainmates.
Agile / Agile Project: Ratings / Business Analysis / Product Management / Software development
Posted on:
APR: Corporate Goals
Corporate Goals for the Product We have two corporate goals for our agile project. One of them directly drives the features and functionality, and the other one is a driver of a constraint on the implementation approach. Both types of goal are relevant. A process that relies on structured requirements […]
Flashback
Posted on:
Flashback: A Year Ago This Week on Tyner Blain [2006-01-27]
A look back at the best from a year ago.
Requirements
Posted on:
Abstraction And “Requirements”
I don’t know how many of our readers have reached a conclusion to this debate, but we have for now. Thanks to everyone who has contributed to, enjoyed, or at least tolerated this ongoing discussion. Roger had some good comments in our previous article – we’ll try and address one of his points here. His point, I believe, is that using the word “requirements” to describe multiple levels of abstraction in the definition of a product is a bad thing.
Requirements
Posted on:
Requirement Naming – Stick A Fork In It?
The discussion about requirements and the naming of things continues? Can we stick a fork in it already? Maybe, but probably not. Catch up on the cross-blog discussion with Roger and Adam.
Product Management / Requirements
Posted on:
Valuable and Functional Requirements
Roger asked some interesting questions on one of our previous posts about market and product requirements. In a couple recent articles, we presented some specific examples to clarify the semantics and language of different types of requirements. Roger asks six questions about functional and non-functional requirements in the comments on the last article. In this article, we answer them.
Product Management / Requirements
Posted on:
From Market Requirement To Product Requirements
We looked previously at an example of market analysis, defining first a market opportunity, and then a market requirement. We wrote an article a while ago about how to go from an MRD to a PRD. In this article, we will look at the journey from our market requirement to associated product requirements. And thanks, Roger, for throwing down the gauntlet.
Requirements / Software development
Posted on:
Alphabet Soup – Requirements Documents
This is my requirements document. There are many like it, but this one is mine. My requirements document is my life. [Kubrick, with some editing]. Michael provides a comparison of requirements documentation formats seen in the wild. A good companion to our earlier piece, Michael provides some “what to expect” guidance about how different companies use the different documentation formats. Check it out.
Communication / Product Management / Requirements / Software requirements specification / Writing
Posted on:
Requirements Documents – One Man’s Trash
…Is another man’s treasure. There are many different ways to document requirements when developing software. And there is a proliferation of requirements documents – MRD, PRD, SRS, FRS and design documents. Everyone has a perspective on what each document represents, and each person on the team has a unique perspective on what questions the document answers.