One of the elements of design we need to consider for our agile project is the interface that our users will be using. We need a way to survey our users to get this data. We are using the data from visitors to Tyner Blain as a presumably representative sample […]
Agile / Agile Project: Ratings / Product Management / Requirements / Requirements gathering / Requirements Models / Software development / Software requirements specification / UML Modeling / Use Cases
Posted on:
APR: Mixing It Up With Design And Requirements
With a definition of the important use cases for our agile project, we can move to the logical next step – which is what exactly? Prototyping.
Agile / Agile Project: Ratings / Business Analysis / Product Management / Requirements / Requirements Models / Software development / Use Cases
Posted on:
APR: Prioritizing Use Cases – Vote Three Times
In our agile project case study we defined corporate goals and user personas, and from our understanding created a list of use case names. We refined those use cases into use case briefs, filtering out some of the use cases (for the first revision) narrowing the list to six use […]
Agile / Agile Project: Ratings / Business Analysis / Product Management / Requirements / Requirements Models / Software development / Use Cases
Posted on:
APR: Use Case Briefs
Each of the use cases defined as part of our use case names post is described at a high level of detail here. The goal is to get a broad view of the domain for our project so that we can focus on the most important elements. This is a […]
Agile / Agile Project: Ratings / Business Analysis / Product Management / Requirements / Requirements Models / Software development / Use Cases
Posted on:
APR: Use Case Names
In our agile programming case study, we have two corporate goals, but one of them (learn Ruby on Rails) only drives constraints, not requirements. The other goal is to make it easier for people to find and read great content in our niche. This makes the documentation of goal-driven use […]
Agile / Agile Project: Ratings / Interaction design / Software development / UX
Posted on:
APR: Persona Development
The last step in our agile software development project was documenting our understanding of our users. In this article, we will define the personas that we will use to guide our design and requirement development. This definition of personas is built by combining our experiences in consulting, product and program […]
Agile / Agile Project: Ratings / Prioritization / Product Management / Requirements / Software development
Posted on:
APR: Scope and Vision – Vote On It
In the discussion on our article about understanding users as part of our agile software development case study, Rolf raised an interesting question about the scope and vision of having people rate articles: I’m wondering what an ‘article’ is. Does it have characteristics? Is it just some piece of knowledge […]
Agile / Agile Project: Ratings / Interaction design / Product Management / Software development / UX
Posted on:
APR: Understanding Our Users
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 […]