In-House App Development Accelerator Guide - Apple

More documents

Recommendations

Info

Creating a Scope of Work To help you stay focused and communicate the process, your plan should include a central scope-ofwork document that includes all project resources, goals, objectives, timelines, and key deliverables. This is an important guide to the project for all stakeholders. The scope of work can incorporate preliminary technical requirements for your app, as well as fl owcharts or visual diagrams to help communicate the intent of the app concept during the development phase. Requirements • Scope project • Obtain approvals • Assemble team Assemble Your Team Design • Architecture design • Project plan built • Initial wireframes • Developer sizings Code • Training • Coding of app • Design and graphics • Test cases • Unit testing Verification • Testing on devices • Automated UI tests • Bug fixes • Design review/tweaks • Stakeholder walkthrough Release • Internal release of app • Stakeholder signoff • Maintenance plan As with any project, you’ll want to assemble a team of contributors who each share a stake in the success and outcome of your app project. Some participants may be your internal customers (a line-of-business owner or user group), and others will be tasked with owning specifi c parts of the development process itself (designers, developers, technical architects, and so on). Ultimately, you want to align the team roles and responsibilities with the project timeline and milestones discussed in the prior step. For example, because design is a central element of any iOS development project, you’ll want to make sure you have a design team (or resources to match). Di∂ erent groups may have di∂ erent points of participation and interest in the outcome, so it’s good to document those roles so that everyone can stay abreast of responsibilities along the way. Planning • Design • Development • Deployment Example: Typical Project Team Executive Sponsor Primary stakeholder, responsible for strategic plan Project Leader Tracks schedules, timelines, and overall scope of work User Experience Architect Responsible for framework of user interaction model and user process flow/journey User Interface Designer Responsible for app visual design, graphics, and identity Technical Architect Responsible for infrastructure, security, and data access models IT Manager Responsible for deployment and life-cycle management of apps Line-of-Business Owner Primary stakeholder and app user Product Manager Delivers the app, manages requirements, and reconciles business needs with solutions Development Manager Technical lead and project manager Developer Responsible for overall technical architecture and coding 6
Outsourcing Development If you don’t have su∑ cient in-house resources, consider outsourcing all or part of the development work. Outsourced developers can also present you with a portfolio of their work that could spark new ideas. Of course, to be successful, the outsourced team needs a thorough understanding of your project— everything you’ve determined during the planning process—and regular interaction with you and your in-house team. Discuss your needs and make sure they understand what your objectives are. Review the application defi nition statement and carefully review your project details. And be sure right from the start that you’ve established clear, two-way communication and a process for keeping in touch. You need to defi ne the role your outsourced provider will play, just as you would a member of your internal team. Align their roles and responsibilities to the project plan and timeline so that you can communicate clearly about which aspects of your project they’ll deliver. In-house team responsibilities Outsourced developer responsibilities Requirements Release Design Code Verification Some outsourced partners can help you through all elements of the project, from initial requirements to fi nal deployment. Others may focus only on writing code. It’s good to explore these capabilities and services with your outsourced provider, whether or not you ultimately contract with them. It can help you evaluate their strengths and also inform how you shape the relationship. Planning • Design • Development • Deployment Quick Tip: Selecting an Outside Vendor • Meet multiple vendors. • Review existing work, including apps on the App Store; note app ranking and user comments. • Evaluate skills and capabilities, for example, is all coding done in house? • Ask for references. • Disregard one-size-fi ts-all ethic or generic multiplatform approach. • Focus on UI design, high-quality art, and the app “journey.” • Discuss maintenance and life cycle of app beyond version 1.0. • Ask about IT infrastructure experience. “ We use outside contractors for several di∂ erent pieces. And it depends really on the need of the app. If there’s a very specifi c look and feel, we’ll go talk with contractors who have made things that are similar because we know that they have expertise in that already. In turn, we can give a higher-quality product to our sta∂ or to our customers.” —Todd Schofi eld, Standard Chartered Bank 7
Page 1 and 2: In-House App Development Accelerato
Page 3 and 4: Creating a great app requires a gre
Page 5: Creating an Application Defi nition
Page 9 and 10: 3. Submit to Apple. Once you’ve s
Page 11 and 12: Design matters. Creating a basic iP
Page 13 and 14: Prioritize When an iOS app establis
Page 15 and 16: iPad vs. iPhone If you’re plannin
Page 17 and 18: With iOS you can deliver content an
Page 19 and 20: Integrating shared data. iOS provid
Page 21 and 22: Integrating Web Content into Native
Page 23 and 24: Keychain Services Apps Core Service
Page 25 and 26: Instruments. The Instruments applic
Page 27 and 28: It’s important to note that a pro
Page 29 and 30: network confi gurations and securit

In-House App Development Accelerator Guide - Apple

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?