Kevin Brennan recently posted his presentation from BA World Toronto (hat tip to Ryan). It’s a great presentation, with compelling imagery. Kevin raises an interesting point – are BA’s doomed to obsolescence? Kevin cites outsourcing and agile as two developments that might make BA’s irrelevant. With outsourcing, your company risks […]
Agile Development of Use Cases
We proposed a strategy for developing use cases as part of an agile development methodology last week. In this article, we will look in more detail at that proposal, and also look at a specific way to apply agile techniques to the development of the use cases. What we propose is essentially incremental development of use cases, and starting what comes next as soon as you can.
Flashback: A Year Ago This Week on Tyner Blain [2006-03-31]
A look back at the best from a year ago.
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.
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.
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?
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?
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: A Year Ago This Week on Tyner Blain [2006-03-24]
A look back at the best from a year ago.
