Technology Solutions

Hybris Methodology

Regnant Implementation methodology is a proven system for the implementation of omnichannel B2B & B2C solutions.
Aligned with a complementary business change management plan, it allows the implementation team and the client to share a development system that:

Minimises risk by leveraging the 80/20 rule and avoids too many ‘bells and whistles’ that can risk budgets and timeframes

Builds upon hybris Accelerator frameworks where appropriate

Incorporates comprehensive governance processes to ensure a quality outcome

Establishes appropriate customer and partner expectations upfront

Provides focused and clear roles for the customer, contiigo and 3rd parties

Leverages best practices of proven methodologies (e.g. Agile); hybris professional services recommendations; and contiigo’s own intellectual property

hybris-methodology (1)

Agile development/best practice methodology

Regnant is committed to continuous improvement in our methodology, learning from our experiences, rather than stringently following a challenged process. Our methodology is therefore an evolution of our experience, with a strong background in industry best practices. We believe the delivery of software projects is a team collaboration, requiring transparency and communication, and most of all nurturing an environment of trust amongst all members of the team and the relationship with our stakeholders.
Specific to our development methodology, we believe in delivering highest business value items in small iterative steps. Solution design is part of the process, continually and iteratively occurring throughout the engineering phase, and working with the development team.
We also believe that delivery of our client’s requirements should be of the highest quality. To do this, we believe the development team should understand the development stories before starting development of the story, and clearly understand it’s acceptance criteria. It is crucial that the nominated Product Owner from the client be a part of this process and agree to the story descriptions. Our developers are then able to make use of a test driven approach (TDD) to verify that the code they write meets the requirements of the user story.
Our technical leads perform code reviews to ensure that developers are delivering code according to the standards and best practices. In addition to the code level unit testing and code reviews, we believe a QA engineer should be part of the multi-skilled development team, and functionally test all stories that have been implemented before closing them. Upon completion of a sprint, only stories that have met the acceptance criteria, and pass the QA processes can be considered “done”. These stories are then demonstrated to our client to allow them the opportunity to ask questions, and see the working solution.

Project governance

Our project method is underpinned by strong governance to ensure risk is reduced:

Regnant will setup and maintain a project Risk, Issues and Dependencies log to track each of these items throughout the life of the project. The log will contain information about each such as description, mitigation plan, impact/likelihood, risk rating, owner, and due date.

The Project Manager regularly reviews the risk log and development leads to ensure mitigation plans are in place and tracking to plan.

Regnant also conduct regular risk & issue workshops with the project team to identify, review and plan our risk mitigation strategy. These workshops are usually held once per sprint and the risk, issues and dependencies log is reviewed at least weekly as part of our preparation for the weekly project status report.

The Regnant weekly status report will include the top 2-3 risks, issues and dependencies from the log. This provides the wider project team with visibility into the current key risks and issues for the project along with the mitigation plan for these.

Solution Development

Requirements are documented as User Stories and a project “Backlog” is developed in JIRA Suite. User Stories are prioritised according to business goals within the Backlog.
Development is iterative and organised into sprints. Continuous “Grooming” of the Backlog allows identification of priority stories, blockers and new requirements

Coordination with hybris Professional Services

Regnant actively involves hybris professional services team for Design Review, Code review and Readiness approval to assure transparency and confidence in the solution being implemented

This is a unique website which will require a more modern browser to work!

Please upgrade today!