Establishing project milestones and estimated delivery dates are also part of these early discussions. Timeframes and delivery were part of the proposal and selection process, but those were only rough estimates. When you start reviewing the project in detail with a developer the project schedule should always be part of the discussion. Start with an overall, major project milestone list or map to share with the developer. For example, if an app has three major functional sections, finishing and demonstrating each segment is a milestone (with a partial payment), The final integration is a milestone. Testing and acceptance will be the last milestone. Each of these milestones may be three weeks apart – at least as a starting point.
While discussing the projects, more milestones may come up or time frames altered.Again, be open-minded when the developer makes suggestions, but stick up for your interests as well.
A PERT chart shows the sequential relationships between project and develop-ment activities. Include completion dates as well
At the end of reviewing the app design, a complete milestone and schedule that both parties agree to should be a required outcome.
Toward the end of these initial project discussions, consider creating a PERT chart. PERT charts show the relationship between project milestones – particularly what milestones must be complete before starting other activities, and what activities can be done separately in parallel. For example, you don’t have to wait for the app code to be complete before you start taking steps to market or distribute the app. We will explain this in more detail in the marketing chapter.
It is important to remember the importance of going into great detail when reviewing the app concept design. Go over every screen and function along with every user action and response until you are sure the programmer understands your intentions.Do not assume the programmer will intuitively know or understand something.While you should be delivering detailed screen shots (if not the graphics themselves) and functional flow charts, some nuances may not be captured in these documents, or something may have been overlooked that will be seen here. Take careful notes and mark up descriptions, drawings, and charts as needed.Then the developer(s) will have carefully reviewed and accurate documents to work with as they begin writing the code.
"The Space-O team were great to work with. Every part of the process went as per the agreed schedule, and the finished prototype met, and in most cases, exceeded my expectations. While Space-O wasn't the most price competitive of the quotes I received, the quality of their work, professionalism, and product, was well worth the additional cost. Highly recommend, and will continue to use their services for future projects."
"I wish to acknowledge the high quality of your team effort in executing the project for Dollens Electric. Seldom do things go as initially imagined and requested, an such was the case for this project. However, the capability of the end product fills the need. The professionalism of your team an company is impressive. I appreciate that, as it reduced the time required from our staff. Thank you for a good effort; please feel free to use me as a reference customer if it is useful. Best Regards, Steve Dollens"
"I hired Space-O to help build my fitness and food log mobile apps. Professional, knowledgeable, and skilled, Space-O delivered a detailed mock app and a fully featured product that launched successfully. The team communicated well and readily grasped concept and intent. Their communication and ability to understand requests were top-notch. I was most impressed with their professionalism, their extensive end-to-end knowledge, and their design capabilities."
Space-O Infoweb Inc, Suite 100-B 8585 E. Bell Road Scottsdale, Arizona 85260 +1 (650) 666-3071