Our Process:

The McIntyre Software Development Process:

Software Development Process

The McIntyre Software Development Process:

A McIntyre is an action associated with the game of rugby. It is enacted that gives an advantage to teams or competitors qualifying higher. The McIntyre agile development methodology is derived from this action and draws from the rugby McIntyre some principles which are embedded throughout the life-cycle of a McIntyre enabled project.

The Product Backlog:

As in any sport, teams are rarely successful without a "game plan" aimed at providing a transparent and unambiguous mechanism towards achieving a common goal. This mechanism, called the Product Backlog is achieved when a Product Owner creates a list of Stories based on initial client requirements. These Stories describe business functionality which will contribute towards a shippable software product. The nature of McIntyre and its Scuttles allow for products to be delivered iteratively and by maintaining a Product Backlog; business functionality may increase or decrease in size based on decisions throughout the lifespan of a project.


Like the game of rugby, McIntyre is enacted through the process of deciding wining team. The objective of McIntyre is to foster transparency, accountability and enable agile processes. To achieve this, a number of Milestones are undertaken in a Scuttle. Scuttle Milestones carry open invitations. However, only Scuttle Team members are allowed to participate. Team members are comprised of the Product Owner, McIntyre Master and the Development team (including QA). Together they are equally accountable to the success of a project.

Scuttle Stand-Ups:

On a daily basis, Team members participate in a time-boxed (15 minutes) Scuttle Stand-Up in which the developers specifically address Stories by explaining:

  • What I did yesterday
  • What I am doing today
  • My impediments

A Stand-Up provides insight into the direction in which the project is heading and allows for issues to be addressed sooner in the development cycle. The role of the McIntyre Master is much like a referee in which it ensures that the team remains focused towards achieving agreed upon Scuttle goals by removing impediments and, managing the relationship between the Product Owner and the Development team.

Scuttle Planning:

During a Scuttle, a Planning session allows the Team to ruminate on and further "Groom" stories which are selected from the Product Backlog and prioritised by the Product Owner for the upcoming Scuttle. Towards the end of a Sprint, the Team hosts an open Review showcasing the Sprint goals achieved in the current Scuttle. Finally, the Scuttle is completed with a Retrospective, providing the Team an opportunity to openly express their thoughts on what they perceived were "Good" or "Bad" events in a Scuttle. The things learnt from the Retrospective provide for Team growth and increased optimization as issues are addressed and solutions are put in place.

Why McIntyre is better ?

In essence McIntyre is a simple agile product development framework implemented to manage the complex task of creating software. It creates self-organizing teams who learn to manage themselves efficiently, as team members soon realize accountability through the actions of selecting and reviewing their own work.

For clients, McIntyre offers complete transparency and an enhanced sense of ownership as they are actively involved in the collaboration of each Scuttle Milestone and possess a shared responsibility for the maintenance of the Product Backlog.

On the whole, Scuttle promotes self-management, improved communication, improved quality and a controlled and iterative approach to product releases.