Last week, Ivan Chalif, a product manager / blogger, tapped into a thread criticising product managers for not adopting and espousing agile, or at least rapid-release techniques. In this article we look at Ivan’s comments and one of the articles that he referenced. We also share our own perspective and an alternative analysis of what may have happened.
Continue reading Is Agile Bad For Software Development?
In lieu of an article today, we’re updating our theme. There are a bunch of minor improvements, and two major ones. New visitors and regular members of the community should both benefit from the changes.
Continue reading Updated Theme With More For You
People who are new to software, requirements, or testing often ask “What’s the difference between a use case and a test case?” This article answers that question, by building on earlier articles about use cases and use case scenarios. At the soundbite level, each use case has one or more scenarios, and each use case scenario would lead to the creation of one or more test cases.
Continue reading The Difference Between Use Cases and Test Cases
We created a series of Visio 2003 stencils last September to support our series of articles on BPMN. Anthony Britton has created a Visio 2002 version of the stencils for people who do not have Visio 2003 (or Visio 2007).
Continue reading Free BPMN Stencils for Visio 2002
It is easy to mix up the definitions of use case and use case scenario. A use case represents the actions that are required to enable or abandon a goal. A use case has multiple “paths” that can be taken by any user at any one time. A use case scenario is a single path through the use case. This article provides an example use case and some diagrams to help visualize the concept.
Continue reading What Are Use Case Scenarios?
Here’s an example of a use case that has some system complexity. The user interacts with the main system that we are describing. The system also interacts with two external systems. This use case example shows how to describe the steps that demonstrate all interactions with the system.
Continue reading Sample Use Case Example
Jacques Murphy Describes the Four Phases of Implementation at productmarketing.com.
When selling a software product to a customer, your customer tends to go through four phases of emotional satisfaction with their purchase.
- Oh Boy! – Excitement about the anticipated benefits of using your software.
- Oh Shoot! – Discouragement about the anticipated work required to use your software.
- Oh Well – Resignation that the work just needs to be done.
- Oh Wow! – Excitement about the realized benefits from your software.
Jacques writes a fun, easy, oh so true article about this experience. We’re adding a visual.
Continue reading Four Phases of Implementation
Joel on Software writes a great article about how to set the price for your software to maximize profits.
Joel does a good job of explaining and exploring the economic theories behind pricing and balancing supply and demand. He then dives into market segmentation and how it applies to pricing. Finally, he addresses the marketing elements of pricing and perceived value. He takes us on a fun journey with an enjoyable read, even if he doesn’t get to the conclusion we all need. The thoughts and analysis are still helpful when thinking about pricing your software.
For more actionable advice, and generally everything about pricing, check out the Dollars and Sense blog by Reuben Swartz. A lot of good stuff there! He has a categories on software pricing, pricing strategy, and a lot more.