Protocycling Approach

“Protocycling” leverages the rigor of the Waterfall method while pacing rapidly though design and getting to code faster with incremental releases as found with Agile.

Princeton Information believes that the more time spent early in the software development cycle planning and designing leads to greater efficiency and predictability at later stages of a project. Our overall objective is to spend enough time on the analysis and estimating activities upfront in order to define a sound plan and to create a project framework to ensure development phases run smoothly following a more traditional Waterfall approach.

We often blend the basic disciplines of Waterfall and Agile to utilize an approach we call “Protocycling” that leverages the rigor of the Waterfall method while pacing rapidly though design and getting to code faster with incremental releases as found with Agile.

Using the Protocycling Approach, we begin to define the majority of the requirements and create the high level Business Requirements Document and Project Plan in the early stages of the engagement, continuously refining the requirements during the build cycles.

The joint team refines the business processes as we step through the development of the system. Frequent deliveries and releases, including clickable wireframes and lightweight integration of subsets of the system to the pilot team allows for constant feedback from the business.

This process offers many advantages including:

  1. Accelerates the adoption and buy-in of the new system by making users a part of the creation process
  2. Quickens the learning curve on the new technology and new business process
  3. Improves speed-to-deployment delivering maximum business value
  4. Helps mitigate risk using the rapid and frequent feedback mechanism including retrospectives
  5. Keeps the project team focused on the needs of the client
  6. Knowledge transfer occurs more naturally in a controlled and progressive manner