Agile #1 – Gathering requirements

Build what the user wants

A good user requirements process will help us build the software the users have in mind and creates a shared understanding among all the shareholders of the product.

Conversation – primary form of communication

  • Developers and business work together toward the development process
  • Just Enough – Just In Time (Progressive refinement) – contain the 3C (the card, the conversation, the confirmation)

Adaptive – Discover user needs vs. collect user needs

We don’t know the needs, we will discover them. The requirements will change.