Scoping call presentation_rev_4_mary
- 1. implement derek’s gothic Standard template for all font? banner placeholder CIMs but they just need imp his black background vs. -add both bb logos john to swap the Clemson our white background; does sent banner with their his background incur more school’s custom banner Bb Mobile Central loading/lag time/bites? -Pretty slides up with and add, if available, images, screenshots, their CIM headshot. formatting, etc. Implementation Font size inconsistencies throughout Project Scoping Call for CIM Headshot Here
- 2. Who’s on the Call? • Client: • Project Lead: Name, role • Project Team: Names, roles • Client Implementation Manager: • CIM: Name, role • CIM’s Manager: Name, role
- 3. The Process 30,000ft View 1. Client selects Modules for this phase with Sales 2. Client and CIM flesh out details on scoping call 3. Client provides data and asset deliverables 4. CIM checks deliverables and builds a test version 5. Client gives CIM the “thumbs up” 6. CIM distributes the app to iTunes, Marketplace, etc. 7. Client is happy 8. BB Mobile Team is happy
- 4. How We Get to “Happy” ✓Great Product ✓Great People ✓Great Plan ✓Great Execution
- 5. Have John rework the content in the first t wo bullets so Great Product it’s less about details and more about the product. Right now it’s too redundant of the scoping call and plan with the mods • Discuss Modules and Platforms chosen for this Phase • Establish business drivers: • Dates, capabilities, other • Your data + our framework + teamwork = Successful Mobile App!
- 6. Great People • Client: • Project Lead, Project Team (Data Owners), Stakeholders • BB Mobile Team: • CIM • Sales Rep • Engineering
- 7. Great Plan • Scope • Define the Modules and platforms • Owners • Assign who is responsible for each task • Timeline • Follow closely as delays will cause shifts • Workflow • Define process for each part of app build
- 8. Great Execution • Client: Data gathering • CIM: Validation • CIM/Engineering: Configuration • Client: Approval of test build • BB QA: Testing • CIM: Submission • Client/BB Mobile: Phase wrap-up
- 9. Let’s Begin! 1. Setup • Basic app info (app name, project URL, support e-mail, etc.) • Design assets (icons, backgrounds, etc.) • Developer account(s) set up (iTunes, Google Marketplace, etc.) 2. Modules • Determine options and functionality • What would users benefit from the most? (Look at the following slide to view which Modules link together!) • List best practices per Module • Determine readiness 3. Distribution • Marketing materials and content
- 10. Modules Linking the Pieces Together
- 11. Setup 1. Basic application information • App name, area code, school colors • support e-mail, project URL 2. Design assets • Backgrounds • custom Module icons • Main icons for stores 3. Developer accounts • iTunes: test devices, certificates • Android, Blackberry, Palm
- 12. Setup: Icons • Required in multiple sizes • “@2x” = high retina display (icon on right) • Specific naming requirements • 12 character limit • Provide .psd/vector version of icons • Helpful for editing purposes • Make backgrounds of icons transparent so that the background color can be adjusted without effecting icons
- 13. Modules General Data Validation Most of your data comes in a few different formats. There are some basic validation steps you should take for each data type regardless of the Module. • Web Services • XML • CSV • Icons • Video • Naming conventions
- 14. Courses • Which option: Web service, XML, or CSV? • Are you ready? What work needs to be done? • Best Practices: • Workflow - not too deep • Will you be linking to building data in Maps? • Need web service if you want to provide current course enrollment
- 15. Courses: Sample Page 1: Department (ex: Monument School of Medicine) • Page 2: Subject (ex: Surgery) Categories Page 3: List of Courses (ex: Surgery 101, Surgery 500a, etc.) • Course Details Page 4: Course Detail -or- Page 1: Semester (ex: Spring 2011) • Sample XML Page 2: Department Page 3: Subject Page 4: List of Courses Page 5: Course Detail
- 16. Directory • Which option: LDAP, web service, XML, or CSV? • Are you ready? What work needs to be done? • Best Practices: • Do not send private information • Will you be linking to building data in Maps? • Whitelist our servers if LDAP is behind firewall • If this is the first time you have made student/ faculty data open to public, make sure you have a policy in place to allow this
- 17. Directory: Sample • Directory search • Directory results
- 18. Athletics • Which option: 3rd party service or custom XML? • Are you ready? What work needs to be done? • Best Practices: • Use existing JumpTV or other service • Will you be linking to building data in Maps or Directory for contact info?
- 19. Athletics: Sample • List of teams with IDs • Three feeds: 1. News 2. Schedules 3. Scores
- 20. News • Which option: RSS or ‘Enhanced’? • Are you ready? What work needs to be done? • Best Practices: • Use ‘Enhanced’ XML feed for better user experience
- 21. News: Sample • List of categories with IDs • Feed for each category can be a mix of RSS and ‘Enhanced’
- 22. Video • Which option: 3rd party or custom XML feed? • Are you ready? What work needs to be done? • Best Practices: • Use existing YouTube channel • Ensure videos are streamable
- 23. Video: Sample • List of categories with IDs • Can use YouTube channel
- 24. Images • Which option: 3rd party (flickr) or custom XML? • Are you ready? What work needs to be done? • Best Practices: • Images not wider than 1,000 pixels
- 25. Images: Sample • List of categories with IDs • Need thumbnails for custom XML
- 26. Events • Which option: Web service, XML, or .ics? • Are you ready? What work needs to be done? • Best Practices: • Ensure stop and start date/time are separated out • Will you be linking to building data in Maps or Directory for contact info?
- 27. Events: Sample • List of categories with IDs • Can use .ics (iCal) format
- 28. Maps • Which option: Google MapKit or custom map? • Are you ready? What work needs to be done? • Best Practices: • Start with Google MapKit if time is a factor • Geo codes (long/lat) need to be exact • If using Google MapKit, check how much detail is available for your location • Places, Tours, and Transit plug-ins are for iOS platform and custom map only
- 29. Custom Maps: Sample • Accurate map image • Building data to 5 decimal places • Unique building IDs to allow mapping from other Modules
- 30. Library • Which option: 3rd party (WorldCat) or web service? • Are you ready? What work needs to be done? • Best Practices: • Do not advertise as a full-fledged catalog search; meant to be a quick, basic search on a small screen
- 31. Library: Sample • Searchable fields • Library contact info
- 32. Get Help • Only option: CSV (we provide a template) • Are you ready? What work needs to be done? • Best Practices: • Keep it simple and relevant
- 33. Get Help: Sample John to add GH Content - currently Athletics content • List of teams with IDs • 3 feeds: News, Schedules and Scores
- 34. Links • Only option: Custom links with custom icons • Are you ready? What work needs to be done? • Best Practices: • If more than one link, think about creating a hosted landing page and link to that • Make sure targets of links are mobile friendly
- 35. Links: Sample • Custom icon • Mobile friendly • Don’t clutter springboard
- 36. Transit Plugin • Only options: For iOS platform and custom maps • Are you ready? What work needs to be done? • Best Practices: • Review Google Transit data formats • Exact building data is important
- 37. Note to self: add a Transit screenshot Transit: Sample • All routes are made of stops • We provide you a tool to draw routes
- 38. Places Plugin • Only options: For iOS platform and custom maps • Are you ready? What work needs to be done? • Best Practices: • Can provide categories of places • Link to Directory for contact info • Link to building data to show on Maps
- 39. Places: Sample • List of categories with IDs • List open and closed times separately for each day
- 40. Tours Plugin • Only options: For iOS platform and custom maps • Are you ready? What work needs to be done? • Best Practices: • Add tours for different audiences • Actually walk tours to make sure they make sense to a pedestrian or driver
- 41. Extra bullet point with Tours: Sample no info; see if John meant to add something else • List of categories with IDs •
- 42. Distribution For submission of your application, there are several items that you will need to create: • App descriptions • Short video • Screenshot • Keywords
- 43. Intro to Jira • Dashboards • Show statuses • Show timeline • Show description section with data validation steps • Show statuses • Show milestones
- 44. Come back to for a more enhanced image Intro to Jira
- 45. Next Steps • Access to Jira • List of tickets with owner of each deliverable • Details of this call added to associated ticket in Jira • Timeline provided by CIM • Client reviews tickets and gathers data • Ask questions as needed • Will have a call as needed to consolidate questions
- 46. Note to self: Look at email template John sent me regarding follow up email to client after scoping call and below notes from meeting with John. --send this as a follow up email after the call, thank them and attach this Assignees for org of owners of data. create follow up thank you email of Deliverable recap of meeting, list the basics of Owner what was discussed, this attachment, General Icons/Images etc Courses Data Directory Data Maps Data Events Data News Data Library Data Athletics Data Video Data Image Data Get Help Data Links Data Places Data Transit Data Tours Data iTunes, Android, Blackberry dev site access Verbiage for submissions
- 47. THANK YOU! • Excited to begin! • Ask questions; don’t struggle. • Keep us in the loop with any delays.
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: \n
- #9: \n
- #10: \n
- #11: \n
- #12: \n
- #13: \n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: \n
- #20: \n
- #21: \n
- #22: \n
- #23: \n
- #24: \n
- #25: \n
- #26: \n
- #27: \n
- #28: \n
- #29: \n
- #30: \n
- #31: \n
- #32: \n
- #33: \n
- #34: \n
- #35: \n
- #36: \n
- #37: \n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: \n
- #43: \n
- #44: \n
- #45: \n
- #46: \n
- #47: \n
- #48: \n