Agile Development Methodology Comparison

Posted on:

Agile project management has entered the mainstream – incremental delivery is now common and (should be) expected for any new software development project. Which agile development methodology should you use on your project? There are at more than ten to choose from. What makes them different? The risks that they try to address.

How To Write Use Case Preconditions and Triggers

Posted on:

Use case writing is key to effective requirements management. Each use case represents a single idea or logically grouped behaviors. When you define a use case, there are several mistakes you can make. Preventing those mistakes is the first order of business. The second order of business is making sure that the use cases in the system work together. This requires an understanding of the context in which the use case happens. To fully understand a use case you have to know what is promised to be true before the use case happens, as well as what causes the use case to happen. These are subtly different.

Product Management and User Experience

Posted on:

There’s a buzz going around about the conflict and collaboration between product managers and user experience professionals. It started with a pair of articles co-written by Jeff Lash and Chris Baum. In short, with a user-centric view of products, both roles are responsible for the success of the user-interactions. Who makes the decisions?

Project Scheduling – 80% Done, 80% Remaining

Posted on:

Johanna warns us that there is “no such thing as percent complete” when it comes to tracking status on a project. Your managers and customers want to know percent complete – and there is a way to report it. Project planning and scheduling involves walking this fine line.

Scheduling Product Releases

Posted on:

When you define a product roadmap, you also define the release dates for your product. Change happens. Your market changes, your customers change, your requirements change. Unpredictable events happen. Your competitors release a new killer feature, your developers have an epiphany (or run into a roadblock). Should you change your release schedule?