Continuing the articles in our agile project case study. The next step in our agile requirements management process is to develop an understanding of our target users. We believe a user-centric design approach is important. The user interface should conform to the way our users think about what they are […]
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 […]
Agile / Agile Project: Ratings / Product Management / Project Management / Software development
Posted on:
APR: Scope and Vision
To define the boundaries for our agile project, we need to define the scope. To provide a guiding framework for the rest of the work, we need to document the vision. We could create heavy-weight scope documents and vision documents. And we could run them through reviews and get approvals […]
Agile / Agile Project: Ratings / Product Management / Requirements / Software development
Posted on:
Agile Software Development Experiment
We’re considering trying an experiment in agile software development at Tyner Blain. There aren’t (m)any examples of agile software development that we can watch and study that include agile requirements development. Many people still think that agility and requirements management are mutually exclusive. If the responses to this post don’t […]
Agile / Product Management / Software development / Test Automation / Testing
Posted on:
Is Agile Bad For Software Development?
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.
Product Management
Posted on:
Four Phases of Implementation
Jacques Murphy Describes the Four Phases of Implementation – Oh Boy!, Oh Shoot!, Oh Well, Oh Wow!
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?
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.
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.