- Next week – prep for final presentations
- Facebook Messenger looks to shed bot baggage
- Sonar & contextual messaging
- Telegram botprize
Let’s pick up where we left off last week and see where you are with your projects.
Why document your projects?
What kinds of things should you document?
- Equipment requirements
- Architectural requirements
- Software requirements
- Maintenance procedures
- Update procedures
- Expenses and estimated budgets
Project Documentation List
For each member on your team, take turns role playing that you are your client partner. As the client partner, imagine what you would need to know if you were to actually try to implement your team’s project. Start a list with the first role player, adding to it with each additional role player.
Draft Project Implementation Documentation
- Create a new Google Drive document and title it Project Implementation Documentation
- Scour over your list, looking for common themes
- For each theme, create a heading in your document; for example, if your project requires usernames and passwords to be able to use it, include a section on user names and passwords
- Other headings might include, hardware requirements, software requirements, maintenance requirements, marketing and promotion, etc.
Open Discussion & Project Workshop
Continue working on your projects.
Together with your team, make sure your Team Page is up-to-date and includes the following artifacts:
- Project name
- Project description
- Team members
- Project flows
- System Personas
- Project Implementation Document
- Any other screen shots or documentation your team has developed
- Create a new slide in your Design Notebook and title it “Project Status for April 29”
- Write a brief summary paragraph of your teams progress this week
- Write a second paragraph outlining your team’s goals for next week
*Submit the link to your Design Notebook to Canvas before we meet again next week