<center> <hr/> <a href="https://monadical.com" class="btn btn-default btn-lg">Company Site</a> &nbsp; <a href="https://monadical.com/portfolio.html" class="btn btn-default btn-lg">Portfolio</a> &nbsp; <a href="https://monadical.com/blog.html" class="btn btn-default btn-lg">Blog</a> # Transparent Work Process - Guide Book *Originally created 2020-04-03 by Ana & Luka @ Monadical.com* --- </center> [TOC] --- :::success **This document is a living handbook guiding our approach to transparent communication at Monadical.** - Without you, we wouldn't have a great company, team and culture we have. - When you work with us, we become a part of your team. - You rely on our expertise and project organization to get the job done right the first time. - If a team wants to accomplish something amazing, **transparent, efficient and direct communication is the Key**. - We believe in **total transparency, and great communication**. - That is why we have created this guide book. ::: **Contents:** [TOC] --- ## Work Process :::info There are 5 parts of each project management process that we use: **Creativity, Strategy, Building, Quality control, Communication.** This unique approach allows our team to deliver a well-tested, beautifully-documented codebases with complete deployment, growth, and maintenance stories. **See below the 5-step process we use with every project we take on.** ::: ### 1.0 - Creativity Stage :::info We define a problem and an idea. We begin to imagine possible solutions, gather ideas, and creative answers to your unique challenges. We start forming a rough plan we will follow to move towards the solution, but we don't finish it yet. We are creative at this stage and we think of bold solutions that require out-of-the-box thinking and the industry expertise. ::: #### 1.1 Our first call - A founder will be on the first call - You'll explain your problem, story and the context/motivation - We'll ask questions to get an understanding of your needs - We'll explain our team, current capacity, our rates, and how we imagine we would approach the project - If it seems like we are a good fit, we move on to #2. Otherwise, we’re happy to offer advice, referrals, or help in any other way we can. #### 1.2 Our second call - Usually we'll have a second call where we go into deeper detail on the project. By now we will have prepared ourselves with any necessary research. - When it seems like there’s a mutual understanding of the underlying business and technical concerns, we’ll move on to #3 ### 2.0 - Strategy Stage: :::info We take creative and bold ideas from the creativity stage and formulate a blueprint for the plan to work. We create a project outline for you that is summarized in a [**Technical Project Review Document**](https://docs.monadical.com/s/B1rXtc7DU). It includes Project Overview, MVP Features Deliverables, Ideal Product Deliverables, Extra Features Deliverables, Development Time & Budget, Risks & Concerns, Technical Overview, Resources, Timeline, Next Steps. The Technical Project Review document is there to make our ideas comprehendible and we use it as a plan to bring your project to life. ::: #### 2.1 Formal proposal - We’ll put together a proposal document. It’ll include a detailed plan of action and an estimated timeline/cost estimate. - [Example](https://docs.monadical.com/s/B1rXtc7DU) #### 2.2 Contract - We have a very simple, human-readable 3-page contract, or we can work with something your attorneys prepare. ***Begin work!*** ### 4.0 Onboarding & Ongoing Communication :::info We actively take each of the steps in the project, create reports and send them back to you. Although we are a software team, we are also a communication team. Each step requires open communciation and active reporting. Because of an efficent communication, we are organized, notice unobvious obvious errors and inneficiences faster, save time and increase whole team's happiness. Every project matters for us and each team member is focused on their own project. The better the communication, the better the end result. ::: ### 5.0 Building :::info In this stage we build a product from the project that we laid out. We code, test, deploy, document the codebase, create growth and maintenance stories with the future in our mind. All good building steps need a quality control, and that's the next step. ::: ### 6.0 Quality Control :::info We inspect the code with an eye for perfection. We look for bugs, improvements, and test the solution for long-term performance. We strive for perfection and want to make sure our end product fits the idea you had in your mind and, most importantly, provides a great solution. Quality control saves time, increases code efficiency and increases our happiness with the end result. We stand behind our code. ::: ### 7.0 Final report ## FAQ <center> <hr/> <a href="https://monadical.com" class="btn btn-default btn-lg">Company Site</a> &nbsp; <a href="https://monadical.com/portfolio.html" class="btn btn-default btn-lg">Portfolio</a> &nbsp; <a href="https://monadical.com/blog.html" class="btn btn-default btn-lg">Blog</a> </center>