Difference between revisions of "IS480 Team wiki: 2013T2 Change-Makers Midterm Wiki"
Line 251: | Line 251: | ||
==<div style="background: #FFCC00; padding: 15px; font-weight: bold; font-size: 100%; 1em; line-height: 0.1em;"><font color="black">Reflection</font></div>== | ==<div style="background: #FFCC00; padding: 15px; font-weight: bold; font-size: 100%; 1em; line-height: 0.1em;"><font color="black">Reflection</font></div>== | ||
− | ===Team Reflection | + | ===Team Reflection=== |
Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki [[Knowledge_base | knowledge base]] and linked here. | Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki [[Knowledge_base | knowledge base]] and linked here. | ||
− | ===Qian Bi Reflection | + | ====Qian Bi Reflection==== |
One cannot underestimate the importance of ensuring that the team stays motivated and healthy! Through my experience as PM, I have learnt that frequent communication is very important to keep the team on schedule. Understanding my team and the issues they are facing allow me to better manage and estimate the team schedule. | One cannot underestimate the importance of ensuring that the team stays motivated and healthy! Through my experience as PM, I have learnt that frequent communication is very important to keep the team on schedule. Understanding my team and the issues they are facing allow me to better manage and estimate the team schedule. | ||
− | ===Rachel Reflection | + | ====Rachel Reflection==== |
I have learnt that while we may almost always want to accommodate to all requests our clients makes, it is important for us to evaluate the difficulty of the functionality, our team's capabilities, time and properly manage expectations. Further, from our user test, I've learnt that what we as developers often think to be simple or easy to use, may not always be so to users. | I have learnt that while we may almost always want to accommodate to all requests our clients makes, it is important for us to evaluate the difficulty of the functionality, our team's capabilities, time and properly manage expectations. Further, from our user test, I've learnt that what we as developers often think to be simple or easy to use, may not always be so to users. | ||
− | ===Benjos Reflection | + | ====Benjos Reflection==== |
Line 267: | Line 267: | ||
− | ===Kean Reflection | + | ====Kean Reflection==== |
Creating an attractive user interface that is well-liked by students is challenging as everyone has their own preferences. I have learnt the importance of user testing and how to improve the user experience of the system with users feedback. | Creating an attractive user interface that is well-liked by students is challenging as everyone has their own preferences. I have learnt the importance of user testing and how to improve the user experience of the system with users feedback. | ||
− | ===Keng Theng Reflection | + | ====Keng Theng Reflection==== |
I have learnt to think ahead on the system design pros and cons when considering client’s requests. While it is good to have cool features on the frontend, some will take up too much resource or require complex designs on the backend. Thinking ahead helps to clarify the requirements, explain the cons and propose alternative solutions quickly. | I have learnt to think ahead on the system design pros and cons when considering client’s requests. While it is good to have cool features on the frontend, some will take up too much resource or require complex designs on the backend. Thinking ahead helps to clarify the requirements, explain the cons and propose alternative solutions quickly. |
Revision as of 19:38, 19 February 2014
Home | Team | Project Overview | Factor | Project Management | Project Documentation | Project Resources | Team Reflections |
Project Progress Summary
Place your Midterm slides link and deployed site link here
For proposal, please see Requrements at the Project Deliverables. This will help us understand your scope. Note wiki policy here.
This page should NOT be too long. It should link to other pages in the IS480 team wiki. Do not repeat the proposal or other wiki information here. However, keep a snapshot of the midterm state. Highlight changes since project acceptance.
Describe the project progress briefly here. Have the project continued as planned? If not, is the team confident to complete? This is a crossroad for the team to make a decision. Proceed with confident or file an incomplete.
Project Highlights:
What unexpected events occurred?
- Team members too busy with other work
- List of requirement changes
- CRUD items replaced with CU/Sync/Archive items
- Business analytics replaced with iPad client
- Took 8 weeks to learn Ruby on Rails
- etc.
Be brief.
Project Management
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
Project Status:
Highlight changes to modules, the completion status (implemented, user testing done, client approved, deployed, etc), the confidence level (0-1 where 0 is no confident of getting it done, 1 is 100% confident in getting it done) and comments (who has been assigned to do it, new scope, removed scoped, etc). Please use a table format to summarize with links to function details.
Task/function/features, etc | Status | Confident Level (0-1) | Comment |
Customer CRUD | Fully deployed and tested 100% | 1 | Fiona |
Trend Analytic | 25% | 0.9 | Ben is researching analytic algoritms |
Project Schedule (Plan Vs Actual):
Compare the project plan during acceptance with the actual work done at this point. Briefly describe a summary here. Everything went as plan, everything has changed and the team is working on a new project with new sponsors or the supervisor is missing. A good source for this section comes from the project weekly report.
Provide a comparison of the plan and actual schedule. Has the project scope expanded or reduced? You can use the table below or your own gantt charts.
Iterations | Planned | Actual | Comments | ||
1 | Customer CRUD | 1 Sept 2010 | 25 Aug 2010 | Fiona took the Sales CRUD as well. | |
Trend Analytic | 1 Sept 2010 | 15 Sept 2010 | Ben is too busy and pushed iteration 1 back | ||
2 | User tutorial | 1 Oct 2010 | Removed proposed by Ben | ||
Psycho analysis | 1 Oct 2010 | New module proposed by sponsor |
Project Metrics:
Sprint Backlog Metrics
Click here to find out how we calculate our sprint backlog score and the action plan.
Bug Metrics
Click here to find out how we calculate our bug score and the respective plan of action.
Overall breakdown of bug score
Distribution of bug severity
Bug severity per sprint
Outstanding Bugs
Sprint | Bug | Severity | Priority |
---|---|---|---|
8 | Page always goes to the top when user saves rather than remain at the anchor | 1 | Low |
11 | Spin-the-Wheel points are not always correct | 5 | Medium |
Project Risks:
Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken.
Risk | Probability | Impact | Mitigation |
Sponsor want to use Joomla instead of Drupal | High | High | Team evaluating Joomla to write an impact analysis report |
Sponsor deployment machine approval and support | High | Medium (now it is low) | Use UPL machine |
Be sure to prioritize the risks.
Technical Complexity:
Describe and list the technical complexity of your project in order of highest complexity first. For example, deploying on iPhone using Objective-C, customizing Drupal with own database, quick search for shortest flight path, database structure, etc.
Quality of Product
Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.
Intermediate Deliverables:
There should be some evidence of work in progress.
Stage | Specification | Modules |
Project Management | Minutes | Team Minutes |
Metrics | Schedule Metrics | |
Requirements | Story cards | CRUD Customer, Trend Analytic |
Analysis | Use case | Use Case Diagram |
System Sequence Diagram | client, server | |
Business Process Diagram | Here | |
Screen Shots | CRUD Customer, Trend Analysis | |
Design | ER Diagram | ER Diagram |
1, 2, 3 | ||
Testing | User Testing | User Testing Documentations |
Not all parts of the deliverables are necessary but the evidence should be convincing of the progress. Try to include design deliverables that shows the quality of your project.
Deployment:
System has been deployed to the school server.
Testing:
1 User Test conducted so far.
CLick here to view our user test documentations and results.
Reflection
Team Reflection
Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.
Qian Bi Reflection
One cannot underestimate the importance of ensuring that the team stays motivated and healthy! Through my experience as PM, I have learnt that frequent communication is very important to keep the team on schedule. Understanding my team and the issues they are facing allow me to better manage and estimate the team schedule.
Rachel Reflection
I have learnt that while we may almost always want to accommodate to all requests our clients makes, it is important for us to evaluate the difficulty of the functionality, our team's capabilities, time and properly manage expectations. Further, from our user test, I've learnt that what we as developers often think to be simple or easy to use, may not always be so to users.
Benjos Reflection
Kean Reflection
Creating an attractive user interface that is well-liked by students is challenging as everyone has their own preferences. I have learnt the importance of user testing and how to improve the user experience of the system with users feedback.
Keng Theng Reflection
I have learnt to think ahead on the system design pros and cons when considering client’s requests. While it is good to have cool features on the frontend, some will take up too much resource or require complex designs on the backend. Thinking ahead helps to clarify the requirements, explain the cons and propose alternative solutions quickly.