The pre-discovery phase of software development is crucial. This phase is about establishing the most compelling need for the platform. Into what it wants to achieve and the implications for the solution, prior to evaluating technical options during discovery.
The key outputs for the discovery phase include High-fidelity UX wireframes, clickable prototypes for core screens, UI designs, and a detailed product breakdown. But these require the following key outputs prediscovery:
To define the scope: The first step is to describe the nature of the underlying process and its users. It requires practical experience with the business context.
To conduct research: Research helps to validate the project. It may include user research, market research, and technical research.
To understand user stories: this means using research guided by experience. And it extends to understanding target users and their needs, goals, and behaviors.
To define feature requirements: Based on user stories, they include functional requirements, performance requirements, and security requirements.
Create a roadmap: including key milestones, deliverables, and dependencies, and should be updated as the project progresses - to keep things purposeful.
Establish a budget: Establishing a budget for the software project 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 software. And it enables technical excellence is discovered for something meaningful. It can be done separately or with our consultancy services.
Steven Faseyiku | Client Services