Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Delivering Office 365 Applications on Short Deadlines (Case Study)

In this case study presentation, Shadeed Eleazer walks through the key details of successfully delivering a staff voting application leveraging Office 365 within 48 hours of design and development time window. Requirements gathering, usability, end user testing considerations are provided in this session.

Libros relacionados

Gratis con una prueba de 30 días de Scribd

Ver todo

Audiolibros relacionados

Gratis con una prueba de 30 días de Scribd

Ver todo
  • Sé el primero en comentar

  • Sé el primero en recomendar esto

Delivering Office 365 Applications on Short Deadlines (Case Study)

  1. 1. Delivering Office 365 Applications ON SHORT DEADLINES SHADEED ELEAZER
  2. 2. What We Will Cover  How to effectively gather requirements with short deadlines in mind  How to quickly decide on development/design/configuration approach  A proven approach to iterative testing and change request within the 72 hour window of application building  How to set up ad hoc testing groups and test scenario suggestions to ensure applications are properly functioning
  3. 3. Requirements in a Time Crunch  What if requirements change at the last minute?  How do you avoid scope creep?  How do you determine which approach to utilize in short period of time?
  4. 4. The Requirements..(The Mission)  System shall allow 1 vote per user  System shall provide pdf of candidate requirements  System shall allow online voting  System shall provide candidate bio information within given section  Users cannot see additional votes  The “ENTIRE” staff needs to access the site and vote  Vice President needs to access voting information at all times
  5. 5. Maximizing the Whiteboard  “If it doesn’t make sense on a Whiteboard…..”  Group sessions as often as possible during design and development process  Get sign-off on the Whiteboard  Take picture of all Whiteboarding sessions. Record if possible  Expect changes to be made. Adopt an iterative mindset
  6. 6. The Approach  How can this application be built with the required features in the least amount of time? (Minimum Viable Project)  How can we keep the design clean and minimalistic?  How can we “hit the bulls-eye” and keep management satisfied?  How do we “educate” an organization new to SharePoint Online?  InfoPath, SharePoint Survey List, Excel Survey, or 3rd Party App?
  7. 7. Design and Usability
  8. 8. Design and Usability  Focus on uniform look and feel to present content  Remove standard SharePoint lists and libraries from homepage  Minimize usage of the Quick Launch bar  Create buttons and use throughout the site layout  Which pages will open in a new tab vs. same browser session  URL redirects
  9. 9. Testing
  10. 10. Adoption  51 employees submitted their vote  Usability of the Staff Voting Poll provided minimal user error  Biggest issue: Logging in with new accounts (less than 4 reported)
  11. 11. Version 2.0  What could we have done better?
  12. 12. Final Thoughts  Collaborate and agree upon requirements  Expect changes. Be flexible  Determine a testing team upfront  Do not build the 8th wonder of the world. Seek for MVP  Determine team to support application during and after launch

×