Our Processes
Bridging the gap between an IoT product idea, lab technology and market-ready products is a team sport. We leverage best agile development practices and newest technologies, customer involvement and collaboration frameworks with engineering excellence throughout.
In EnCata we have adopted the best LEAN development methodologies such as Scrum and Agile, and combined it with our ‘flow process’ philosophy learned from TPS (Toyota Production System). This resulted in a very effective “mix” of project management standards for both design, engineering and manufacturing within EnCata.
In Scrum the hired team provides a preliminary estimate, which is then undergoes prioritization process is a form of a project backlog. Development process is divided into 1-3 week sprints with clear objectives for each.
EnCata uses both the OFFLINE Kanban board and daily startups routinte in additional to project management software. Such that the Project Manager engages on behalf of the product owner to (re)prioritize the backlog.
Any project run under the Waterfall methodology is started from the Research + Discovery phase with the goal to analyse the scope, requirements and objectives and develop a clean and detailed Statement of Work (SOW).
Why do you need to run a discovery phase?
Running discovery phase with EnCata allows you to develop a robust estimation for the project and the SOW. The SOW allows you to requrest estimates from other vendors and development companies, so you don’t end up comparing irrelevant proposals in the first place.
The discovery phase costs from 5 to 10% of the total project cost and it can last as long as a few days, up to 6 weeks - depending how big and complex your project is. In fact, running the Research and Discovery phase allows you to:
- Save up to 50% on your future development and implementation,
- Plan your budget and timelines.
Hardware
- Documented user stories and use-cases
- Technical benchmarking
- Specification development, analysis and validation
- Form and function technical concepting using TRIZ/TIPS
- Risk assessment & analysis
- System / technology / product architecture
- A detailed statement of Work (SOW) for the next milestone(s)
- Preliminary BOM
- Project plan with set milestones based on TRL roadmap
- (Optional) a set of suggested conceptual solutions
- (Optional) a set of design sketches and / or renders
- Estimation for further development and subsystems prototyping
Software
- Project plan
- Software architecture document
- A detailed estimation
- Statement of Work (SOW) or Software Requirements Specificatin (SRS)
- Interactive UI prototype
- Tests / QA plan