Most user stories are written poorly. On one end of the spectrum, there is simply not enough detail and the team remains unsure what to build. On the opposite end, user stories contain too much detail which encourages slavish conformance to the requirements. In both cases, deep understanding of the user’s needs, requirements and priorities remain unspoken, poorly communicated and badly implemented.
Here is the course outline:
To complete this challenge, you will need to be actively working with a Scrum or Agile team. If you are not currently part of a Scrum or Agile team, please contact your instructor to unlock a hidden quest.