Jump to navigation Jump to search
This is a guide for the IS480 presentations (different milestones will focus on different parts)
- Evidence of project management
- Have you updated your Wiki?
- Do you conduct meetings with minutes? And review of the metrics collected? Does it help you to manage the project?
- Do you compare the plan vs actual schedule/scope to improve your change management?
- Are metrics helping you resolve problems before it gets worse?
- List challenges faced (risks mitigated). What are your top 2 risks going forward?
- Value to sponsor
- Are you able to clearly communicate the project problem?
- What value does your system bring to the sponsor/client?
- How does your system capture content from users?
- What usage analytics are you able to present to sponsors?
- Do not proclaim savings, efficiencies, speed, revolutionary, life changing, robustness, all in one, complete solution, etc without going into the details. Have quantitative data to measure your goals.
Quality of product
- Technical complexity
- Are you able to clearly communicate the complexity of the process/workflows/architecture/solution?
- Are the technology solution the best one for the client?
- What is the most technologically complex part of your system? (Don't be afraid to show pseudo/code but you must be able to guide through the complexity)
- Do not proclaim using the benefits of other frameworks as your own. You can say I use MVC, but you must explain how you do it.
- Do you have a diagram that shows all the components/module/3rd party tools/framework/API/design pattern of your code?
- Is it a client server system? Are the data pulled or pushed?
- How flexible/maintainable is your system? Is it hard-coded or uses configuration files?
- Demo & Deployment
- Have fun with your demo! Don't go over every single functions. Login is not your focus/main function. Do a role play or guide us over your main scenario.
- Have you deployed your system to the client’s production environment? Is it on the laptop, IS480 machines, sponsor servers, or sponsor’s cloud account (Amazon Webservices, Google App Engine, Azure, etc.)?
- Can the target users access your system now? Supervisors, reviewers, etc. Is it available to download from App Store, Android market or Market place?
- If it is a PoC (proof of concept), have you worked out the deployment details on a staging/test server?
- User testing
- Are you able to get target users to test your application/system? Do you have personas? Are there multiple roles?
- Include both qualitative and quantitative test data. Don't just ask if they like or will use the system, measure the time they take to complete the task. Have you improved (faster or better) the system (tie it back to the value)?
- Are you testing with real/realistic data?
- Don't test because we asked you to test. Did you learn something you did not know before? (Unknown unknown)
- Practice and time your presentation. If each member handle their own parts without coming together, it is going to be risky.
- What is your X factor? This can change over the milestones. Be ambitious, then be realistic.
- If all else fail, reflect on your learning outcome. Spend sometime here.