OUR APPROACH

BRIDGE METHODOLOGY

Our BRIDGE methodology is a fully agile approach adapted from values and principles of The Agile Manifesto for Oracle Cloud.  Harnessing the power of agile allows CastleBridge to increase flexibility, reduce non-productive tasks, deliver higher quality in a shorter time frame, provide tighter project control and reduce overall project risk.

  • Value 1: Individuals and interactions over processes and tools:
    • The most efficient and effective method of conveying information to and within a team is face-to-face conversation;
    • The best architectures, requirements and designs emerge from self-organizing teams;
    • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
  • Value 2: Working software and business process over comprehensive documentation:
    • Deliver working software and process frequently;
    • Working software and process are the primary measure of success;
    • Continuous attention to technical excellence and good design enhances agility.
  • Value 3: Customer collaboration over contract negotiation:
    • Our highest priority is to satisfy our clients through early and continuous delivery of valuable software and process;
    • Business subject matter experts and our consultants work together daily throughout each sprint;
    • Fill projects with motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  • Value 4: Responding to change over following a plan
    • Welcome changing requirements, even late in the project
    • Agile processes harness change as a competitive advantage

Waterfall
BRIDGE (agile)
Requirements All requirements must be known upfront when clients know the least about Oracle Cloud. This often leads to change request. Requirements are re-prioritized at the start of every sprint. This allows flexibility to adjust requirements during the project.
Requirements Resist Change Embrace Change
Staffing Project resources are assigned for the duration of the project. Typically working on multiple projects part time. Project resources are assigned to the sprint they are needed and are asked to avoid distractions.
Documentation Create and Maintain Volumes of Documentation. Create Just Enough Documentation.
Communication Typically Utilizes both one way and two way communication. Heavily favors two way communication (Face to Face, Video Chat, Phone).
Meetings Formal Weekly Status Meetings with significant prep. Daily Stand Up Meetings with Online interactive status dashboard.
Teams People are assigned to teams. People are assigned responsibility and form the teams necessary to complete the work .
Testing Structured. Iterative.

DO YOU HAVE QUESTIONS ABOUT IMPLEMENTATION?

SPEAK TO AN EXPERT