Nexient has been a leader in Agile development, automated testing, and DevOps since its inception. We have run hundreds of Agile teams, and as an organization, we’ve learned a great deal. The Nexient Delivery Process is a living methodology that allows us to capture the expertise we gain from each project, and utilize that experience effectively on future projects. All of our projects run retrospectives to evaluate how each sprint or phase went and how we could improve. The insights we gain in these retrospectives become part of our corporate knowledge and reside in the Nexient Delivery Process.
The Ideation and Forming phase of every project ensures that we have the right team building the right project that delivers success. This critical upfront work is meant to both align expectations, and validate the product and technology used by the team. The Client’s business goals and technology standards, as well as Nexient’s technology approach are inputs to this phase. The output is a clearly stated and agreed upon technology approach in which our joint team will execute the project and develop the product.
In this section of the methodology, you will find the tools required to create the right team with their roles and responsibilities, the technology roadmap, and the initial product backlog.
The Strategy and Scope phase sets up teams and projects for success. At a high level, it addresses project design and analysis and aligns stakeholders with the team on the scope and sequence of the project. This phase accomplishes all this with an emphasis on getting the team working on development as quickly as possible.
In this section of the methodology, you will find the tools to define the development methodology/process, and architectural practices that will be used in the project, along with initial user stories and initial definition of the Minimum Viable Product (MVP).
The Development and release cycle is where we rapidly iterate through Agile sprints to create, test, and refine the application or product we are building. We work in small cross-functional teams to execute development sprints, which are typically two weeks each. During these sprints, we build the test cases, the features, and deploy the code to either a production or user acceptance environment. Our teams include developers, quality engineers, product owners, business analysts, and scrum masters. With each sprint, we are able to get feedback from the product owner, and adjust the priorities of the user stories we’ll develop in the next sprint.
In this section of the methodology, you will find all of the critical tools required to set up the development team and environment, to create stories effectively, and to manage the development and testing of the application being built. These tools include guidelines on and templates for ceremonies, coding standards, continuous integration, continuous delivery, and retrospectives.
The production / support section of the process is where we actively support an application in production. In some cycles, we will do this with each two-week sprint. With other projects, we will do several sprints, deploy them to user acceptance environments, and then release to production. Through the end user and application support processes, we will typically find additional enhancements to the application that increase its usability and business value. This feedback loop from the production phase feeds right into the next phase of development and the cycle continues.
In this section of the methodology, you will find all of the tools required to deploy the application to production environments and the processes and tools necessary to support the application, both from an end-user perspective and from a technical perspective. The tools utilized here include continuous deployment processes and checklists, service level agreement templates, and monitoring frameworks and guidelines.
Nexient is at its best when we are accountable for the delivery of a project. Throughout the engagement with clients, we are extremely transparent about the status of the project and the key issues within the project. We use a number of innovative tools to measure status and productivity throughout the Agile development cycle and use those to provide the client with a clear picture of where the project stands.
The tools in this portion of the methodology include templates for key project reporting, service level agreements and metrics as well as monitoring tools for measuring productivity across a project.