A look back at the best from a year ago.
Agile / Project Management / Software development
Posted on:
Agile Release Planning With Games
Leading Answers, an agile project management blog, has a great article that details some agile techniques for release planning exercises. Their article includes explanations and great diagrams.
Requirements / Requirements Models / UML Modeling
Posted on:
How To Use UML Statechart Substates
UML Statecharts can be very effective modeling tools for describing systems and software requirements. They provide a clear framework for identifying business rules. The same business rules often apply to multiple states – defining a commonality for those states. There is an element called a substate in UML statecharts that can be used to make it more obvious that a particular business rule applies to multiple states.
Agile / Business Analysis / Prioritization / Product Management / Project Management / Requirements / Requirements gathering / Requirements Models / Software development / Use Cases
Posted on:
How To Start The Use Case Process For Agile Software Development
One of the goals of agile software development is to deliver value quickly and iteratively. One of the most effective ways to begin the software development process is with use cases. To deliver with agility, you start with the most valuable use case, bang it out, and then move on to the next most valuable use case. How do you know which use case is the most valuable if you haven’t defined all the use cases first?
Prioritization / Project Management / Requirements
Posted on:
Writing Incomplete Requirements
Writing Complete requirements is one of the twelve elements of writing good requirements. Sometimes, you don’t have the opportunity to finish the job, and are forced to write incomplete requirements. How would you go about doing that?
Business Analysis / Product Management / Requirements / Requirements gathering
Posted on:
Three Types of Requirements Gathering
There are many different activities that are a form of requirements gathering. So many that it can be difficult to determine which approach to use in what circumstance. By classifying requirements gathering into three different types of activities we can simplify the choices.
Flashback
Posted on:
Flashback: A Year Ago This Week on Tyner Blain [2006-03-24]
A look back at the best from a year ago.
Design / Software development / Usability / UX
Posted on:
Don’t Make Your Products Too Simple
Joshua Ledwell wrote a short article expressing his perspective on designing software that is neither too simple nor too complex. He also links to some excellent other articles on the topic.
Business Analysis / Product Management / Requirements / Requirements gathering / Requirements management software / Requirements Models / UML Modeling
Posted on:
UML Statecharts and Documenting Business Rules
In yesterday’s article we compared use cases and UML statecharts as tools for discovering business rules. James Taylor asked a question about how we would document those rules, and then followed up my comment response with an article about business rules and RUP. In this article we move the conversation slightly forward – recognizing that we’re slowly entering the ocean of business process management.