Thinking in Stories for Visual Control

Below are my requirements for a “Project” related information RADIATOR in my office. I asked the App Dev leadership team to produce an output based on the below stories. I decided to use stories as I think it helps us think about what’s truly necessary, and allows the team to focus without me suggesting a specific solution (…just like on our teams, imagine that).

I’ve started with an EPIC story, then decomposed toward more granular user stories that can be delivered in pieces.

See anything I’ve missed?

EPIC STORY – App Dev Visual Controls

  • As an Application Development Director,
  • I want:
    • to see my entire project portfolio’s “relevant project data”
    • displayed visually
    • in a simple and cohesive way
    • in ONE location
  • So I can help ensure IT has a healthy, productive, positive, transparent, and delivery focused development organization.

USER STORIES – App Dev Visual Controls

Project Delivery – Roadmap

  • As an Application Development Director,
  • I want to see a projects “functional roadmap” along with ongoing changes
  • So I can help drive delivery and guide execution across our product portfolio.

Project Delivery – Release Plan

  • As an Application Development Director,
  • I want to see a projects release plan
  • So I can help drive delivery and guide execution across our product portfolio.

Project Delivery – Impediment Backlog

  • As an Application Development Director,
  • I want to see a projects impediment backlog
  • So I can see project risk clearly (and early) and help remove impediments at an organizational level when appropriate.

Trends – Cyclomatic Complexity

  • As an Application Development Director,
  • I want to see cyclomatic complexity trends for major projects,
  • So I can help ensure our codebase remains malleable, of high quality, and change tolerant over time.

Trends – Code Coverage

  • As an Application Development Director,
  • I want to see code coverge trends for major projects,
  • So I can help ensure our codebase remains malleable, of high quality, and change tolerant over time.

Trends – Coupling

  • As an Application Development Director,
  • I want to see coupling trends for major projects,
  • So I can help ensure our codebase remains malleable, of high quality, and change tolerant over time.

Trends – Technical Debt

  • As an Application Development Director,
  • I want to see the technical debt backlog and “debt load” trends for major projects,
  • So I can track the health of our technology organization by seeing clearly the rate at which we add and clear technical debt.