Keeping Everyone in the Loop - WPCampus 2018

Transcript

1. Keeping Everyone 
 in the Loop Keeping Stakeholders Informed Throughout

   the 
 Software Development Lifecycle Blog - shawnhooper.ca
 Twitter - @shawnhooper

2. Actionable Conversations Blog - shawnhooper.ca
 Twitter - @shawnhooper 
 Habit

   Builder SaaS Product
 B2B
 Multilingual
 API First
 Lots of notifications via Email & SMS

3. The Players Blog - shawnhooper.ca
 Twitter - @shawnhooper Sales &

   Marketing
 Technical Support & Account Management
 Legal
 Developers
 DevOps
 Translation Providers
 Documentation Team
 API Consumers
 B2B Partners
 End Users

4. New Feature Phases Blog - shawnhooper.ca
 Twitter - @shawnhooper Concept

   Design Development Documentation & Training Launch

5. Concept Blog - shawnhooper.ca
 Twitter - @shawnhooper Wireframes
 
 Sanity

   checking with a few others to make sure ideas make sense
 
 Financial Impact Analysis (if required) Personal Data Analysis (GDPR, EULA)

6. Blog - shawnhooper.ca
 Twitter - @shawnhooper

7. Design Blog - shawnhooper.ca
 Twitter - @shawnhooper Wireframes -> Graphic

   Design 
 Screenshots & Notes to JIRA Tickets and Confluence Pages 
 Don’t forget about other supporting systems

8. Blog - shawnhooper.ca
 Twitter - @shawnhooper

9. Blog - shawnhooper.ca
 Twitter - @shawnhooper

10. Development Blog - shawnhooper.ca
 Twitter - @shawnhooper Wireframes over to

    Graphic Design
 
 Collecting Copy, Images, Video, ALT Tags, Transcripts, Email Notifications, SMS Messages, etc.
 
 Writing Feature Code & Tests Updating Test Data Generators
 Infrastructure Updates & CI/CD Updates
 
 Translation on Standby… 


11. QA Blog - shawnhooper.ca
 Twitter - @shawnhooper Support and Limited

    Users testing in staging Translation Being Done in Parallel Load Testing & Security Testing 
 Able to go back to development if needed

12. Documentation & Training Blog - shawnhooper.ca
 Twitter - @shawnhooper Change

    Log (Detailed) User Guides (Major Features) API Documentation Staff Training Sessions (Support, Sales, etc.) Canned Responses for Help Desk

13. Blog - shawnhooper.ca
 Twitter - @shawnhooper

14. Blog - shawnhooper.ca
 Twitter - @shawnhooper

15. -2 Weeks Blog - shawnhooper.ca
 Twitter - @shawnhooper Site is

    in Staging (Ideally Code Frozen) 
 Documentation & Release Notes Sent to Partners and Support Team w/ Release Schedule

16. Launch! Blog - shawnhooper.ca
 Twitter - @shawnhooper Site goes live

    (off-peak hours) 
 Updated Client-facing user guides published
 
 Support team replying and closing out bug tickets

17. ShawnHooper.ca 
 Twitter: @ShawnHooper THANK YOU! Blog - shawnhooper.ca
 Twitter

    - @shawnhooper