19 Apr 2016

Top reasons to have Software Governance


Development Stage

What needs governance

How do we (or tools/techniques used for) govern?

Business Problem

  • The source of problem statement (real business case vs. developer’s wish)
  • Project roadmap, timeline and resource constraints
  • Process exists to ensure right stakeholders are engaged, agreed upon project roadmap is defined, and resource pool, delivery timeline and risks are identified

Requirement Gathering

  • Use Case and Requirements
  • Effort level and Risks
  • Requirement document reviewed and signed off from all major stakeholders (business, development and testing teams)


  • Alignment with corporate IT
  • Non FRs like Performance, Security
  • Architecture Review


  • Design guidelines
  • Design review


  • Code Quality
  • Feature implementation
  • Code Review
  • Code Coverage
  • Feature Demo


  • Test Plan and Strategy
  • Test Results and Coverage
  • Score card on Non-FRs
  • Review of Test Plan, Strategy, Coverage, and Results
  • Review of Non-FRs score card or compliance report


  • Documents
  • Documentation Review


  • Deployment Instructions
  • Deployment document review
  • Deployment team’s feedback on ease of deployment and 1st few weeks report from production

Service / Maintenance

  • Ease of troubleshooting
  • Number of Customer found defects
  • New feature request
  • Tracking production defects and ensuring root cause analysis done on the same
  • Assess and feed feature requests to next release’s project requirements
  • Process to have regular feedback from service team’s