22/03/2023
The pre-discovery phase of software development is key. It establishes the most compelling need for any platform - before evaluating technical options during discovery.
Let's say the outputs for our discovery phase include High-fidelity UX wireframes, clickable prototypes for core screens, UI designs, and a detailed product breakdown. These need some key outputs pre-discovery:
1.) A defined scope: The first step is to describe the nature of the underlying process and its users - which requires practical experience with the business context.
2.) Research: Research helps to validate the project. And it may include user research, market research, and technical research.
3.) User stories: this means research guided by actual experience. And it means understanding focus users, their needs, goals, and behaviors.
4.) Feature requirements: Based on user stories, they include functional requirements, performance requirements, and security requirements.
5.) A flexbile roadmap: this includes key milestones, deliverables, and dependencies, and will be updated as the project progresses - to keep things purposeful.
6.) An established budget: the budget for the platform is as much about resources of time as it is about financial resources - incorporating all the above.
The pre-discovery phase of software development minimises the potential of building an inefficient or irrelevant platform.
It ensures technical excellence is discovered for something meaningful. And it can be done prior, or via our consultancy services.
Steven Faseyiku | Client Services
Phoenyx
