Process

At NetEngine, we craft solutions that are custom-tailored to your business. We pride ourselves on the flexibility of our software, and its ability to adapt over the course of our partnership.

Flexibilty doesn't belong everywhere. Costs, dates and deliverables are defined in advance. We've created this example engagement to demonstrate the key phases and steps of our process, highlighting the actions and benefits for each.

Workshop

Architect, Salesperson and Customer

  • Analyse unique business opportunities
  • Simplify pre-existing specifications
  • Define prototype

Benefits

  • Bypass the waste of Big Up-front Design™
  • Discover the advantages of our process, our technology
  • Meet the team. Rediscover the whiteboard

Build

Build Team, Architect

  • Develop and design prototype

Director, Customer

  • Define long term success for the project

Benefits

  • Fixed cost
  • Delivered in 2 weeks
  • Witness immediate return on investment

Launch. Collect feedback

Customer

  • Gather prototype feedback from users
  • Challenge earlier assumptions of requirements

Benefits

  • Avoids the trap of feature-creep
  • Values simplicity over complexity
  • Begins product-roadmap going into the build

Strategic Project Planning

Architect, Customer

  • Balance cost of requirements against anticipated ROI.
  • Refine product roadmap. Schedule first sprints.
  • Define acceptance criteria for scheduled features.

Benefits

  • Effectively separates creativity from productivity.
  • Focusses product on "lowest hanging fruit".
  • Documents key decisions, deliverables, and dates.

Sprints 1, 2

Architect, Build Team, Customer

  • Discuss features and acceptance criteria.
  • Clarify any questions directly with the customer.
  • Design optimal implementation. Build.

Benefits

  • Fixed price. Agreed features and acceptance criteria.
  • New features are available in days.
  • Uninterrupted development as a small team radically improves quality.

Strategic Project Planning and Review

Architect, Build Team, Customer

  • Discuss features and acceptance criteria.
  • Clarify any questions directly with the customer.
  • Design optimal implementation. Build.

Benefits

  • Fixed price. Agreed features and acceptance criteria.
  • New features are available in days.
  • Uninterrupted development as a small team radically improves quality.

Sprints 3, 4, 5

Architect, Build Team, Customer

  • Discuss features and acceptance criteria.
  • Clarify any questions directly with the customer.
  • Design optimal implementation. Build.

Benefits

  • Fixed price. Agreed features and acceptance criteria.
  • New features are available in days.
  • Uninterrupted development as a small team radically improves quality.

Strategic Project Planning and Review

Architect, Customer

  • Discuss any deviations from product roadmap since previous meeting.
  • Assess and document impacts of these deviations.
  • Prepare for the upcoming sprints.

Benefits

  • A high-value opportunity to influence project outcomes.
  • Recognises that many customers have separate stakeholders for cost versus scope.
  • Improves communication and accountability.

Sprint 6

Architect, Build Team, Customer

  • Discuss features and acceptance criteria.
  • Clarify any questions directly with the customer.
  • Design optimal implementation. Build.

Benefits

  • Fixed price. Agreed features and acceptance criteria.
  • New features are available in days.
  • Uninterrupted development as a small team radically improves quality.

Build live environment

Architect, Maintenance Team

  • Build an appropriate application environment in line with traffic and redundancy expectations.
  • Automate backup / recovery.
  • Configure 3rd party monitoring tools.

Benefits

  • Durable. Cloud architecture that anticipates failure.
  • Scalable. Infrastructure counts 0, 1, many. We start at many.
  • Secure. Measured performance.

Maintenance Team Handover

Architect, Maintenance Team

  • The NE iteration team will perform a thorough handover of the project to the maintenance team for ongoing support.

Benefits

  • Separates the development of new features from the provision of support.
  • Separation enables priority support that doesn't compromise feature delivery.
  • Enables ongoing maintenance at a reduced monthly fee.

Support

Maintenance Team

  • Respond to support requests for minor changes or bugs.
  • Push updates for review with the minimum of fuss.
  • Deploy continuously and unceremoniously.

Benefits

  • A smooth launch. Your questions answered.
  • No estimates or budgets.
  • If there's pain, we remove it.

Partnership Review

Director, Customer

  • Review partnership so far.
  • Assess past performance.
  • Plan for future business together.

Benefits

  • Provide opportunity for communication above the project-level.
  • Openly discuss expectations.
  • Receive ongoing feedback at a regular interval.

Apply security patches. Update dependencies.

Maintenance Team

  • Keep rails / ruby / gems on the latest versions.
  • Keep the production environment running smoothly.
  • Test the disaster recovery procedure.

Benefits

  • Keep your product secure against emerging threats.
  • Prevents an escalating cost of development over time.
  • An opportunity to share insights from new projects backwards.

Support

Maintenance Team

  • Respond to support requests for minor changes or bugs.
  • Push updates for review with the minimum of fuss.
  • Deploy continuously and unceremoniously.

Benefits

  • No estimates or budgets.
  • Your product becomes your most reliable tool.
  • If there's pain, we remove it.

Strategic Project Planning and Review

Architect, Customer

  • Discuss any deviations from product roadmap since previous meeting.
  • Assess and document impacts of these deviations.
  • Prepare for the upcoming sprints.

Benefits

  • A high-value opportunity to influence project outcomes.
  • Recognises that many customers have separate stakeholders for cost versus scope.
  • Improves communication and accountability.

Sprint 7

Architect, Build Team, Customer

  • Discuss features and acceptance criteria.
  • Clarify any questions directly with the customer.
  • Design optimal implementation. Build.

Benefits

  • Fixed price. Agreed features and acceptance criteria.
  • New features are available in days.
  • Uninterrupted development as a small team radically improves quality.

Apply security patches. Update dependencies.

Maintenance Team

  • Keep rails / ruby / gems on the latest versions.
  • Keep the production environment running smoothly.
  • Test the disaster recovery procedure.

Benefits

  • Keep your product secure against emerging threats.
  • Prevents an escalating cost of development over time.
  • An opportunity to share insights from new projects backwards.

Support

Maintenance Team

  • Respond to support requests for minor changes or bugs.
  • Push updates for review with the minimum of fuss.
  • Deploy continuously and unceremoniously.

Benefits

  • No estimates or budgets.
  • Your product becomes your most reliable tool.
  • If there's pain, we remove it.

Ongoing Project Review

Architect, Customer

  • Discuss any deviations from product roadmap since previous meeting.
  • Assess and document impacts of these deviations.
  • Collaborate around ongoing opportunities for the project.

Benefits

  • A high-value opportunity to influence project outcomes.
  • Improves communication and accountability.
  • Ongoing advice as upcoming technologies enable new solutions.
Prototype Build Launch Maintain
Top