Skip to main content

Estimates & Timeline

Description The estimates and roadmap timeline is set on a project level. See each division and product to have a better understanding.

Roadmap Management​

The roadmap and tasks are managed in GitHub, see each division for a link to thier GitHub Project.

Roadmap​

Description

Expected Outcome By now we want all parties involved to have a better picture of the problem we want to solve, for who we are solving it, and all relevant information. Details & Status Assigned To: you Due: This should take just a few hours to complete but perhaps take a few days to brainstorm. Requirements: Complete canvas Time Frame: One Week Documents: BIDDY | Development Roadmap Status Pending Pipeline New

Reports and metrics​

We will send a report about the project status every Friday so we can show the client and also measure all the progress in comparison to our roadmap.

Working Paper​

These documents exist to keep track of all engineers’ ideas and thoughts during project implementation. We are going to use GitHub Projects to add tasks and detailed documentation related to any thoughts on how to solve technical issues and to each task there will be a place where the engineers can add their solutions. While it shouldn’t be the major source of information, these documents will help us to retrieve highly specific project details if needed.

Standers​

All coding standards are listed in the Garage | Documentation However, to summarize, we will use the best development practices such as Clean Code and Clean Architecture to ensure that any developer who reads the code understands what it does and also to ensure that the code is well-structured and testable. For User Interface and User Experience, our strategy is to follow the UI guidelines of the platform we are currently working on (iOS and Android). This will allow us to spend less time on User Interface and User Experience as well as make use of some components like authentication, navigation, billing and more that we made for all projects. Another benefit of following these guidelines is that we can integrate with other applications being developed on the platform, allowing us to add features and capabilities later on.

The development details have also been excluded from this document for greater elaboration into technical details that may not be necessary for all involved and are specifically meant for technical personnel such as UX designers, developers and the project manager. For the development details, please see Development.

Description The development documentation is designed to outline the development method and to explain some technical aspects. For a full project description refer to 01 SafeDeposit - Documentation.

The full timeline, tasks and product management will take place on GitHub Projects, below are the major milestones & release targets. Start of development | Date Start Testing MVP | Date

Estimates & Timeline Description The full timeline, tasks and product management will take place on GitHub Projects, below are the major milestones & release targets. Start of development | Date Start Testing MVP | Date Roadmap Description The UX Canvas exercise should be performed with the relevant parties, this may include some other steps such as presenting the canvas and scheduling several meetings. Expected Outcome By now we want all parties involved to have a better picture of the problem we want to solve, for who we are solving it, and all relevant information. Details & Status Assigned To: you Due: This should take just a few hours to complete but perhaps take a few days to brainstorm. Requirements: Complete canvas Time Frame: One Week Documents: BIDDY | Development Roadmap Status Pending Pipeline New

Reports and metrics We will send a report about the project status every Friday so we can show the client and also measure all the progress in comparison to our roadmap. Working Paper These documents exist to keep track of all engineers’ ideas and thoughts during project implementation. We are going to use GitHub Projects to add tasks and detailed documentation related to any thoughts on how to solve technical issues and to each task there will be a place where the engineers can add their solutions. While it shouldn’t be the major source of information, these documents will help us to retrieve highly specific project details if needed. Standers All coding standards are listed in the Garage | Documentation However, to summarize, we will use the best development practices such as Clean Code and Clean Architecture to ensure that any developer who reads the code understands what it does and also to ensure that the code is well-structured and testable. For User Interface and User Experience, our strategy is to follow the UI guidelines of the platform we are currently working on (iOS and Android). This will allow us to spend less time on User Interface and User Experience as well as make use of some components like authentication, navigation, billing and more that we made for all projects. Another benefit of following these guidelines is that we can integrate with other applications being developed on the platform, allowing us to add features and capabilities later on.

The development details have also been excluded from this document for greater elaboration into technical details that may not be necessary for all involved and are specifically meant for technical personnel such as UX designers, developers and the project manager. For the development details, please see Development.

Description The development documentation is designed to outline the development method and to explain some technical aspects. For a full project description refer to 01 SafeDeposit - Documentation.