Methodology
Our Process
How we plan, build, test, and support a project, from the first conversation about requirements through deployment and the work that follows.
- Discovery & RequirementsA requirements specification
- Planning & ArchitectureA technical roadmap with milestones
- Development & BuildWorking components you review during the build
- Testing & Quality AssuranceTested software for your approval
- Deployment & Ongoing SupportProduction release and support after launch
Step 01 · 05
Discovery & Requirements
We start with stakeholder interviews and a review of the systems you use now and how your team works with them. From that we settle the project's scope, its technical constraints and the success criteria the finished work will be checked against. Those decisions are recorded in a requirements specification.
Today
- Requests arrive by email and phone
- No shared view of status
Constraints
- Staff sign in with existing accounts
- Works on a phone
Success criteria
- Every request has an owner
- Requesters can see status
Open question: who closes a request?
New application
Request form
Request tracking app
Database
Sign-in check
Status updates
Existing systems
Staff sign-in
Email notifications
Step 02 · 05
Planning & Architecture
With the requirements agreed, we map the system's components, data flows, integration points and security controls, and choose technologies for the project's needs. The technical roadmap sets out those decisions and the project milestones.
Step 03 · 05
Development & Build
The software is built in iterative cycles, with regular demos where you can see working components and give feedback. Code is kept in version control and documented as it is written, so the system can be maintained after launch.
Request queue
| Request | Location | Status |
|---|---|---|
| Leaking sink | Room 204 | Assigned |
| Door lock | Lobby | New |
| Light out | Stair B | Waiting |
Demo feedback Add a “Waiting on parts” status
Changes committed to version control, with notes
- Every request has an ownerFunctionalPlanned
- Sign-in failure shows a clear messageFailure pathPlanned
- Staff log a real requestUser acceptanceWith your team
- Release approvalYour decisionAwaiting your approval
Step 04 · 05
Testing & Quality Assurance
Functionality is checked against the requirements, along with performance and security testing sized to the system and how it will be used. User acceptance testing follows, with the people who will work in the software checking it against their real tasks. You review the tested software for approval before release.
Step 05 · 05
Deployment & Ongoing Support
The production rollout is planned to limit disruption to the people using the current system. After launch, support covers monitoring, bug fixes and performance adjustments as people use the system, and later changes as the business needs them.
Rollout
Pilot group
All staff
Email intake stays open until cutover
After launch
- Monitoring
- Bug fixes
- Performance adjustments
- Later changes
Reported triaged fixed released
Contact IKRC