-
Notifications
You must be signed in to change notification settings - Fork 0
3. Features
Requirements labeled as Must have been critical to the current delivery timebox in order for it to be a success. If even one Must have requirement is not included, the project delivery should be considered a failure (note: requirements can be downgraded from Must have, by agreement with all relevant stakeholders; for example, when new requirements are deemed more important). MUST can also be considered an acronym for the Minimum Usable Subset.
- create event (no login required)
- event local information
- list of countries
- date is optional
- share the event on Twitter (no login required)
- dark theme
- mobile-first design
- show the event with a slug (login required)
- i18n on names and forms (labels + placeholders)
- mongo DB for users and event
- google login provider
Requirements labeled as Should have been important but not necessary for delivery in the current delivery timebox. While should-have requirements can be as important as Must have, they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
- desktop compatibility
- users management
- edit event
- delete event
- show user events
- light theme
- user events image (Cloudinary?)
- unit testing
- login with another providers
Requirements labeled as Could have been desirable but not necessary and could improve the user experience or customer satisfaction for a bit of development cost. These will typically be included if time and resources permit.
- home page with all events
- filter options for events
- share the event on LinkedIn
- save to calendar
Requirements labeled as Won't have, have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, Won't have requirements are not planned into the schedule for the next delivery timebox. Won't have requirements are either dropped or reconsidered for inclusion in a later timebox. (Note: occasionally the term Would like to have is used; however, that usage is incorrect, as this last priority is clearly stating something is outside the scope of delivery). (The BCS in edition 3 & 4 of the Business Analysis Book describe 'W' as 'Want to have but not this time around')
- event image