The Software Development Life Cycle

The Software Development Lifecycle (SDLC) is the framework that we follow to ensure we deliver consistent services for every project. 

The SDLC consists of 8 phases, but not every phase is relevant to every project. The documents produced and timeline for each phase are indicative and may not apply to all projects. This guide is general in nature. Please discuss specific projects with a DE&S Solution Delivery Manager for guidance. 

What you can expect in each phase

1. New/Triage

This phase covers the activities at the beginning of the engagement to provide consistency and structure. The initial request is assigned to a Solution Delivery Manager, who gets everything ready to document detailed requirements.

Who is involved?
  • Business Requestor
  • DE&S SME Contact (SDM/Producer/Principal developer)
  • Solution Delivery Manager (SDM)
Outcomes and Documents Produced
  • Assigned to SDM
  • High level problem statement
  • Engagement checklist completed
Typical Timeline
  • Up to one week
2. Requirements

The requirements phase is about understanding the problem, what we want to achieve and how we might make it happen. In this phase, the Solution Delivery Manager will work with the business and technical teams to produce a Statement of Work (SOW) which address the business requirements. 

A Statement of Work is a document which outlines what activities are taking place, who is performing these activities and the cost. The SDM will work with the business and technical teams to ensure the Statement of Work reflects a viable technical solution that meets the needs of the business.

Once the Statement of Work has been approved by the business, the engagement is ready to kick off.

Who is involved?
  • Solution Delivery Manager
  • Business requestor/project team
  • DE&S Platforms lead
  • DE&S Production lead
  • DE&S Principal developer
  • 3rd party vendor (if external engagement)
  • Other DPHI/DCCEEW teams if necessary
Outcomes and Documents Produced
  • Requirements brief
  • Solution design and estimates
  • Statement of Work
Typical Timeline
  • 2 to 4 weeks depending on complexity
  • Complex engagements may take longer
3. Planning and commencement

This phase is about setting the project up for success. The business and DE&S project teams are formed and come together for a kick-off meeting to discuss initial steps, project governance, timeline, and responsibilities. If there is a vendor involved in the engagement, they will also be involved in the kick-off. DE&S resources are scheduled, the project RACI matrix, timeline and other supporting documents are created and socialised.

From this phase, the production team take over the day-to-day management of the project while the Solution Delivery team maintain project oversight.

Who is involved?
  • DE&S Production lead
  • DE&S Digital producers
  • Solution Delivery Manager
  • Business project team
  • 3rd party vendor (if external engagement)
  • DE&S Master Scheduler
  • DE&S Platforms lead
  • DE&S Digital developers
Outcomes and Documents Produced
  • Project RACI
  • Project timeline
  • Scheduling confirmed
  • Kick off meeting
Typical Timeline
  • Up to 2 weeks
4. User Experience

This phase is for projects involving a user experience design or user research component and aims to prioritise the voice of the end user. In this part of the engagement, DE&S or a vendor will conduct research to understand the end user. Insights from this research will inform product design, such as information architecture (IA) or wireframes. These designs are presented and refined before approval by the business. Along the way, DE&S will review any designs to make sure they are compliant with brand and accessibility standards, and that they are practicable. Sometimes departmental branding teams may need to be consulted in this stage.

Who is involved?
  • Business project team
  • DE&S Digital producers
  • 3rd party vendor (if external engagement)
  • Other DPHI/DCCEEW communications/brand teams
  • DE&S Platforms lead
  • DE&S Digital developers
Outcomes and Documents Produced
  • User research insights
  • User experience designs
  • Design accessibility review
  • Design branding review
  • Design development review
Typical Timeline
  • 1 to 6 months depending on complexity
5. Development

In this phase, developers are busy working to bring your designs to life. They’ll figure out how bring any digital assets online and perform reviews and testing to make sure the product is stable and performs as expected. Sometimes this work may be performed by a vendor. There may be showcases to keep the project teams up to date on how development is progressing. Once the product is ready for functional testing, it can progress to the next phase.

Who is involved?
  • Business project team
  • DE&S platform lead
  • DE&S Digital developers
  • 3rd party vendor (if external engagement)
  • Digital producers
Outcomes and Documents Produced
  • Web environment set up
  • Code review
  • Unit testing
  • System Integration testing
  • Technical briefing
  • Showcases
  • Solution design
Typical Timeline
  • One week to >12 months depending on complexity
6. Quality Assurance

This phase is all about making sure the service meets the requirements developed at the start of the engagement. DE&S facilitates training, testing, and sets up ongoing analytics and reporting. Testing is the most crucial and underrated part of digital delivery. Everyone who is involved in the project has an obligation to test, including developers, producers, testers, customers, and their key stakeholders. This can be the most involved stage of a project for all team members, as testing thoroughly can be time consuming.

Testing in this phase includes:

  • Functional testing to ensure the asset functions as intended
  • Accessibility testing to make sure the asset is accessible to everyone
  • Penetration testing to identify any cybersecurity vulnerabilities
  • Load testing to make sure the asset can handle the demands of users

In addition, DE&S will guide the business to perform User Acceptance Testing (UAT). In User Acceptance Testing, the product owner will engage with the product as if they were an end user, and make sure there are no issues with the user experience. Once User Acceptance Testing is complete, DE&S will seek formal business approval to deploy the asset to the production environment.

Who is involved?
  • Business project team
  • DE&S Production lead
  • DE&S Platforms lead
  • DE&S Digital Developers
  • DE&S Producers
  • DE&S Data Analyst
Outcomes and Documents Produced
  • Content team training
  • Accessibility testing
  • Functional testing
  • Regression testing
  • Penetration testing
  • Reporting and analytics configured and tested
  • UAT test plan
  • UAT
  • Test outcome report
  • Load testing
Typical Timeline
  • Up to three months depending on complexity
7. Ready for service

In this phase, the final steps to release the product to the live production environment are taken.  Technical documentation is compiled and the final showcase takes place.

All deployments require Digital Information Office (DIO) Change Advisory Board (CAB) approval. DE&S will facilitate the CAB process on behalf of the business at this stage.

Once the product is formally approved for release by CAB, DE&S and the business, it will be deployed to the production environment. DE&S will perform final Build Verification testing to ensure everything went smoothly in the deployment. Typically there is then a warranty period where any issues resulting from the deployment are fixed. At this stage, any supporting documentation is finalised and the engagement is wrapped up.

Find out more about the CAB process.

Who is involved?
  • Business requestor
  • DE&S Production lead
  • DE&S Platforms lead
  • DE&S Digital developers
  • DIO Change Advisory Board
  • DE&S Digital producers
Outcomes and Documents Produced
  • Technical documentation
  • Final showcase
  • Change Advisory Board approval
  • DE&S approval
  • Business approval
  • Production deployment
  • Post-deployment testing
  • Complete project documentation
Typical Timeline
  • Up to one month
8. Managed Support

Digital assets are not set and forget, they require continual support and maintenance to ensure they remain secure and stable. In this phase, DE&S will put together a support agreement that details how much will be provided for your product, who will provide it and how much it will cost. For new products, sometimes the support agreement will be part of the initial Statement of Work. 

Support agreements typically cover a 12-month period and contain all of the ongoing costs for keeping the product online. A new support agreement will be prepared as the current agreement nears expiry.

Who is involved?
  • Solution Delivery Manager
  • DE&S Platforms lead
  • DE&S Digital producers
  • DE&S Digital developers
  • Business project team
Outcomes and Documents Produced
  • Support agreement
  • Ongoing maintenance and support
Typical Timeline
  • 12 months