Kilimanjaro/UseCases: Difference between revisions

Cockburn suggests an ocean metaphor to help give an idea about the granularity of user stories.  Since we're "climbing Kilimanjaro," the following might make a better fit:

Peak - The highest-level stories describing our ecosystem in an abstract sense across the whole of Mozilla.  The steps for the main success scenarios in these cases will consist of other use cases.  Peak use cases map to enterprise or business level.

Altitude - These stories are high-level but are mostly high-level within a team.  These use cases will also consist primarily of a few other use cases.  Altitude use cases map mostly to business or system use cases.  They can also be user-goals that stretch across teams.

Base Camp - These are bread and butter use cases that describe the main scenarios and work flows.  They likely have steps that are use cases in other teams, but will mainly consist of implementation steps for a team.  This maps to user-goals and are actions that can be completed in one sitting.  Anything that can't be completed at a sitting or a few steps is an altitude or summary level goal.

 

Gear - These are low-level, technical use cases that go all the way down to implementation details.  These types of use cases are at the task level.  These will only get a fully dressed use case if clarity is needed particularly across teams. Most often these end up being implementation details.