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 […]
Administrivia / Agile / Agile Project: Ratings / Software development
Posted on:
Agile Project: Ratings – Administrivia
This is an administrative post, to help organize the articles in our agile software development experiment. The feedback has been positive so far, so here we go…
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.
Agile / Requirements / Requirements gathering / Requirements Models / Software development / Use Cases
Posted on:
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.
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.
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?