Feature Planning - TACC/Core-Portal GitHub Wiki

Proposed in 2021-02. Expounded upon on 2021-03-04.

Dev BA & UI BA

The BA (Business Analyst) role is split between two roles:

  • Dev BA (Development Business Analyst): served by the Development Manager and the Project Manager
  • UI BA (UI & UX Business Analyst): served by a UI Developer

New features, or enhancements, should be planned at least one sprint in advance of the sprint on which they are worked.

  1. Receive stakeholder wants. Sources:
    • Dev BA
    • Design
    • Developers⁰
  2. Understand stakeholder wants. Participants:
    • Dev BA
    • (for interfaces) Design
    • (for interfaces) UI BA
  3. Understand development solutions. Participants:
    • Developers
    • Dev BA¹
    • (for interfaces) UI BA¹
    • (for interfaces) Design¹
  4. Finalize requirements.
    • Dev BA (or Developers)
    • (for interfaces) UI BA (or Designers)
Footnotes

⁰ Developers become technical users, so they can notice room for improvement and explain it clearly.

¹ These participants can be optional if feature is:

  1. simple enough,
  2. documented well enough, or
  3. already familiar to other participant(s).

² Depending on availability and familiarity, others may finalize requirements on behalf of the relevant BA.

⚠️ **GitHub.com Fallback** ⚠️