--- type: Website Page title: "Our Process | Pixeldust Interactive" description: "See how Pixeldust Interactive takes website and software projects from discovery and a clear SOW through agile production, UAT, launch, and project closeout." resource: "https://pixeldust.net/our-process" tags: [pixeldust, website] status: stable sources: - id: canonical-page resource: "https://pixeldust.net/our-process" title: "Our Process | Pixeldust Interactive" --- # Our Process | Pixeldust Interactive > See how Pixeldust Interactive takes website and software projects from discovery and a clear SOW through agile production, UAT, launch, and project closeout. ## Source - [Open the canonical human-readable page](https://pixeldust.net/our-process) - [Browse the Pixeldust knowledge index](https://pixeldust.net/okf/index.md) ## Page content A clear path from idea to operation # Our Process We combine agile flexibility with clear scope, visible decisions, and defined approval points. You see the work as it develops, know what comes next, and understand what is required to move forward. [Start a project inquiry →](https://pixeldust.net/inquiry) See every phase Delivery path 01 Discover 02 Define 03 Build 04 Prove 05 Launch CLEAR GATES REVIEWABLE WORK Built for visibility ## Agile Delivery Without Ambiguous Commitments Projects change as teams learn. That is useful. Uncontrolled scope, unclear approvals, and invisible work are not. Our process leaves room to adapt while keeping the business goal, responsibilities, budget, and next decision visible. Defined outcomes Reviewable increments Written approvals Practical handoff The complete journey ## Nine Phases, One Accountable Process Each phase has a purpose, a concrete output, and a clear condition for moving forward. [Discuss your project →](https://pixeldust.net/inquiry) 01 Understand ### Qualification and Discovery We confirm the business need, desired outcome, users, budget, urgency, and overall fit. Stakeholder discussions, research, and technical assessment clarify requirements, constraints, risks, and measurable success criteria. - Business objectives and users - Requirements and priorities - Risks, constraints, and success measures 02 Define ### Solution Definition and Statement of Work Discovery becomes a recommended solution and an approval-ready Statement of Work. The SOW defines deliverables, timeline, responsibilities, pricing, assumptions, exclusions, acceptance criteria, and change control. - Recommended solution - Scope, milestones, and commercial terms - Approval and change rules 03 Organize ### Project Initiation and Planning We begin with a kickoff, confirm decision-makers and communication, collect required access and assets, and organize the delivery plan. Depending on the work, this includes user flows, architecture, content planning, a prioritized backlog, and release planning. - Roles and working cadence - Access, assets, and dependencies - Backlog and release plan 04 Build and verify ### Iterative Production and Quality Assurance Work is delivered in short, reviewable iterations. Each cycle includes planning, design or development, internal testing, demonstration, feedback, and refinement. Quality assurance covers the agreed functional, usability, accessibility, performance, security, integration, and device requirements. - Reviewable working increments - Internal QA and defect correction - Controlled scope changes 05 Prove readiness ### User Acceptance and Operational Readiness Designated client users validate the solution against the approved requirements. In-scope defects are corrected and retested while users, administrators, documentation, production content, data, access, and support procedures are prepared for launch. - Client-led UAT scenarios - Training and documentation - Production content and ownership 06 Approve ### Acceptance and Go-Live Readiness After successful UAT, the client formally accepts the deliverables. Together, we review stakeholder approvals, production configuration, backups, migration, security, analytics, support coverage, communications, and rollback planning. - Written acceptance - Launch checklist and ownership - Documented remaining items 07 Release ### Go Live The approved solution is deployed to production. We complete smoke testing, validate critical customer journeys, confirm integrations and analytics, and verify that the experience is publicly or operationally available as intended. - Production deployment - Critical-path validation - Live availability confirmed 08 Stabilize ### Hypercare and Stabilization For an agreed period after launch, we monitor the live solution, address launch-related defects, and confirm stability under real-world use. New enhancements are evaluated separately so stabilization does not become an undefined second project. - Post-launch monitoring - Launch-defect resolution - Stable transition to normal operations 09 Close and continue ### Project Closing and Ongoing Support We confirm completion, transfer documentation and ownership, reconcile access and finances, review lessons learned, and transition remaining responsibilities. When ongoing support is included, the project moves into a defined maintenance and optimization relationship. - Final handoff and reconciliation - Lessons learned and success review - Support or maintenance transition Clear decision points ## Testing Is Not the Same as Acceptance Separating these gates keeps responsibilities clear and prevents “almost finished” from becoming a permanent project status. 01 ### Quality Assurance Pixeldust verifies that the solution works against the agreed technical and experience requirements. 02 ### User Acceptance The client verifies that the solution supports the intended business workflows and users. 03 ### Formal Acceptance The client confirms in writing that the contracted deliverables satisfy the agreed criteria. 04 ### Go-Live Readiness Both parties confirm the people, systems, data, support, and contingency plans are ready. Change without chaos ## New Information Can Change the Plan Agile delivery makes learning useful, but it does not make time and budget unlimited. Feedback within the approved scope is planned into the work. Requests that change the deliverables, cost, or timeline are documented and approved through the agreed change-control process. Start with the real business problem ## Plan a Website or Software Project Tell us what needs to work better. We will help define a sensible first step, the likely effort, and what success should look like. [Start a project inquiry →](https://pixeldust.net/inquiry) [Book a call](https://pixeldust.net/book) [^canonical-page]: Content derived from the canonical Pixeldust Interactive page linked above.