Project Governance

Throughout any UserCentric project, we provide a tight governance approach that reduces project risk, ensures communication is clear, and that any project issues or blockers are quickly surfaced and resolved.

BOOK A MEETING arr Contact Us

Our Delivery Principles

Practical Project Governance

We deliver digital products that transform businesses and markets.

While we are happy to work within your existing processes, we typically use a Scrum Agile methodology, using 2 weeks sprints with standard sprint plan / standup / retrospective ceremonies. All work in progress is visible by a shared JIRA or Trello scrum board. Separately, for some organisations a monthly Steering Committee is established involving a UserCentric Partner and your senior executives to discuss any strategic discussions around budget, team, deliverables etc.

Software development is inherently difficult to completely plan ‘up front’; e.g. many features may not have been visually designed or documented at a high level of fidelity at the start of the project.

To address this, we employ a delivery model based on the “Total Team” philosophy, which includes the following principles:

  • Customer focused
    Our highest priority is to satisfy the customer through early and continuous delivery
  • Evolving landscape
    We welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
  • Fast feedback
    We deliver working outputs frequently, from a couple of weeks to a couple of months, with a preference towards the shorter timescale.
  • True partnership
    Business people, experience practitioners and developers must work together daily throughout the project.
  • Team trust
    We build projects around motivated individuals. We give them the environment and support they need, and trust them to get the job done.
  • Co-located
    The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. If that’s not possible, we use collaborative tools such as Google Meet and Slack.
  • Focus on Scope
    This is about prioritising the most critical aspects for delivery and ensuring that time and effort is optimised accordingly.
  • Measure progress
    Working solutions are the primary measure of progress.
  • Consistent delivery
    Agile processes promote sustainable development. The sponsors, developers, experience practitioners and users should be able to maintain a constant pace indefinitely.
  • Autonomy
    The best architectures, requirements, and designs emerge from self-organising teams.
  • Process feedback
    At regular intervals, the team reflects on how to become more effective, then tunes and adjusts accordingly.
  • Setting team goals At regular intervals, the team reflects on current goals and if we need to re-align.