Project Delivery Process

How we work
One of Orange11’s key success factors for delivering projects on time and within budget is the use of an agile process. Orange11’s preferred development approach is based on an iterative development model known as Scrum.

Scrum divides the design and development work into time boxes known as sprints. Each sprint typically consists of 2-4 weeks, depending on the specific project characteristics.
 

Orange11 development methodology
The use of a tried-and-tested methodology is a key factor in every project’s success. At Orange11, we have years of project experience and have tailored our methodology in a way that ensures success and achieves the highest amount of business value to our customers

Our methodology is based on two pillars: the use of Scrum and our strong and proven engineering practices. This powerful combination is what makes our methodology so effective.

 

Scrum in practice
In practice, Scrum boils down to several important roles and concrete meetings. The main roles are that of the Product Owner and the Scrum Master. Meetings consist of a planning meeting, an estimation meeting, a review meeting and sprint sessions and of course a daily standup meeting.

A customer appoints a Product Owner as the single point of contact who represents the customer and its stakeholders to streamline all communications and to avoid any miscommunications. The Product Owner meets with the development team at the beginning and at the end of each sprint to discuss new features and planning. Prior to the sprints, the Product Owner sets mandates for decision-making and also sets the scope and priorities for the upcoming sprint.

Orange11 appoints a Scrum Master that works closely with the development team. This person is responsible for enforcing the Scrum process, making sure it is used correctly and maximizing its benefits. The Scrum Master’s primary role is to facilitate and protect the team, ensuring the team is provided with the information and resources it needs to successfully deliver the sprints goals/deliverables. The Scrum Master also facilitates the communication with the Product Owner.

Each sprint starts with a planning meeting where the Product Owner meets with the development team to discuss the highest priority features. Following this, during an estimation meeting, the development team estimate time required per feature. Subsequently, the sprint is planned in by selecting the highest priority set of features that can be accommodated within the allocated time.

The development team has a short daily stand-up meeting during the sprint (max. 15 minutes) to discuss progress on a daily basis. As part of the daily stand-up meeting a burn-down chart will be updated. This chart shows the progress of the current sprint (planned vs. actual).

At the start of each project, rules are established to define when a feature is "done". This includes the process of code reviews to enforce these rules. New features are not considered complete until they meet with these criteria.

The team presents the new features that were completed in the sprint during a review meeting. The Product Owner attends this meeting and other stakeholders are encouraged to join. After the review meeting, the team has a retrospect meeting to evaluate the sprint. During this meeting the team evaluate what went well in the last sprint, and what can be improved upon.

At the end of each sprint, a new increment of the system will be deployed to a user acceptance testing environment, where it can be accessed by all stakeholders for the purpose of testing and providing feedback.

In summary

Scrum provides a minimal and focused set of roles, meetings and practices to provide the following benefits to our customers:

• Maximum Return On Investment (ROI) through prioritization
• Incremental delivery of working software
• Feedback into new requirements and priorities
• Quality standards are built-in
• Self improving
• Reliable planning
• Removes sources of waste.