After an no prescription doxycycline antibiotics inexcusably long delay, here is another post on one of the no prescription doxycycline antibiotics sessions from Agile 2011. This one, Agile Thinking for Business Analysis: Going Beyond User Stories generic orlistat in the philippines was presented by Steve Adolph & Shane Hastie.
The premise of the no prescription doxycycline antibiotics session was that although User Stories are the “industry standard” way of documenting requirements in agile approaches, they by themselves are no prescription doxycycline antibiotics insufficient to fully explain the problem space and solution constraints, by design. To get a no prescription doxycycline antibiotics full picture of what the team is trying to deliver, you no prescription doxycycline antibiotics need to progressively elaborate the information, starting with an understanding of the no prescription doxycycline antibiotics scope & context, the no prescription doxycycline antibiotics proceeding to epics and stories, which act primarily as a planning mechanism, and no prescription doxycycline antibiotics finally providing greater detail through the use of acceptance criteria.
The key points I pulled from the talk:
- When it comes to analysis, don’t through the no prescription doxycycline antibiotics baby out with the bath water. In other words, there is no prescription doxycycline antibiotics still some use for models in agile to drive understanding, just don’t spend a no prescription doxycycline antibiotics lot of time making them look pretty. They are tools to no prescription doxycycline antibiotics aid conversations, not the only means of communication.
- The questions we are no prescription doxycycline antibiotics trying to answer should drive the model we want to no prescription doxycycline antibiotics use. Choose wisely.
- Write use cases at the level of intent, not content (thanks Shane for that poetic nugget of wisdom)
- A handy way of remembering quality constraints (non-functional requirements): “PERFUM”
- Performance
- Efficiency
- Reliability
- Functionality
- Maintainability
My favorite quote coming out of the session, Shane’s reference to a 200 page specification document as the “Tome of uncertainty”.