HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: AUSTIN Final Wiki"

From IS480
Jump to navigation Jump to search
Line 78: Line 78:
  
  
Compare the project plan during midterm 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.
+
Comparing our project schedule during the acceptance with the actual project progress, our team is pleased that all initial functions and additional functions have been completed. However, our team has made minor adjustments to the schedule based on the additional functions to cater to all stakeholders.
 
 
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.
 
 
 
{| border="1"
 
|- style="background:blue; color:white"
 
|| Iterations
 
|colspan="2" align="center"| Planned
 
|colspan="2" align="center"| Actual
 
|| Comments
 
|-
 
 
 
|rowspan="2"| 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
 
|-
 
 
 
|rowspan="2"| 2
 
|| User tutorial
 
|| 1 Oct 2010
 
|colspan="2"|
 
|| Removed proposed by Ben
 
|-
 
 
 
|colspan="2"|
 
|| Psycho analysis
 
|| 1 Oct 2010
 
|| New module proposed by sponsor
 
|}
 
  
 
===<font color="#3B5888" size = "4">Project Metrics</font>===
 
===<font color="#3B5888" size = "4">Project Metrics</font>===

Revision as of 13:19, 22 April 2012

Project Overview

Since 30 August 2011, our team has gone through all the milestones and has successfully deployed our solution for use by the client. The team has completed:

1. Web Application

2. Windows Basic/Monitor Service

3. Windows Verifier Service

4. Windows Publisher

5. User Testing with ESPN staffs

6. Documentation for ESPN


Project Highlights

During the entire project execution,there were some unexpected events or changes which forced the team be proactive and implement alternative solutions as below:

S/No Event Actions Taken
1 Promotion of Person-In-Charge Due to the promotion of the person-in-charge and increased workload, the team has to re-schedule our weekly meetings with the client and cater to his change in job scope in order for the project to be deployed successfully and to update the client progressively on the project in obtaining his feedback and any need for changes or improvements.
2 Change in project requirements As the project progresses, there are a couple of major changes that include the addition of new features that is important to ensure a smooth video uploading process by the end-users. Since the schedule has been planned earlier based on the initial requirements, the team has to re-schedule and re-priortise the tasks after the addition to ensure that the major features and tasks are completed first before proceeding to the minor tasks based on the client's timeline.
3 Several deployments due to environmental and coordination factors Due to the difference in environmental factors from the client's workplace, the team has faced major difficulties for successful deployment as planned earlier in the schedule. These environmental factors have greatly affected the entire deployment process as since the team was not informed of the different factors, the team has to change the environmental factors from the initial stage and seek help and guidance from our supervisor,Prof Kyong, due to the steep learning curve that requires immediate action. Thankfully, with the help of Prof Kyong and Google, the team has managed to deployed the solution successfully after several attempts.


Project Challenges

As the end-product of this solution is a real-life deployment that is to be used worldwide, there are several criterias that are important to the client and in doing so, there are some challenges faced by the team during the development process.

  • Webdrive


  • ASP.Net 4.0 Framework coupled with ADO.Net LINQ


  • Effective communication and team-work

Due to the improved workload and changing requirements faced by the team,it is important for the team to communicate well with the different stakeholdes, such as client and supervisor, to update them consistently on the project process and any difficulties faced by the team in meeting the requirements. This has been a challenge for the team as each stakeholder and member

  • Essential adjustments for successful deployment

The major challenge faced by the team is the constant adjustments needed to ensure successful deployment. As it will be real-life deployment, the team has to understand the necessary factors for deployment where minor things such as version difference will affect the deployment of the solution to the client's workplace.


Project Achievements

Despite the challenges and difficulties faced by the team, the team is pleased that there are still some achievements such as:

  • Enhanced knowledge of the technology used and introduced by the client that will benefit the team in future use
  • Better understanding of the client's video uploading process and how do the end-user ensure that it has been transmitted succesfully to consumers
  • Better coordination between the stakeholders and team and the team has learnt how to manage all stakeholders well other than just meeting their requirements.

Project Management

Project Schedule (Plan Vs Actual)

Comparing our project schedule during the acceptance with the actual project progress, our team is pleased that all initial functions and additional functions have been completed. However, our team has made minor adjustments to the schedule based on the additional functions to cater to all stakeholders.

Project Metrics

To measure the team's project progress, the team has implemented the Schedule Metrics to monitor the time taken for the different phases and to ensure that the team is following the schedule as predicted.

AUSTIN Schedule metric.jpg

Most of the tasks during the Development Phase have been completed according to schedule as the team has been well-balanced in ensuring that the tasks as completed as planned. However, after the Midterm, the team has faced several setbacks that require re-scheduling of the tasks a couple of times in order to ensure that the team is able to get the whole backbone of the system up and be ready for cloud deployment to be launched on 29 February 2012.

The team has made good use of the schedule metric that was developed during the initial stage, which has helped to weigh the importance of the tasks that have been delayed and allow the team to implement the necessary action plans to bring the team back on track.

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.


Project Deliverables

List the artifacts produced for this project. The entire deliverable can be submitted in a separate thumb drive, web repository or place in the IS480 team wiki.

Stage Specification Modules
Project Management Minutes Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7
Metrics Bug metrics
Requirements Story cards CRUD Customer, Trend Analytic
Analysis Use case overall
System Sequence Diagram client, server
Business Process Diagram
Screen Shots CRUD Customer, Trend Analysis
Design ER Diagram 1, 2, 3
Class Diagram 1, 2, 3
Testing Test plan instructions
Handover Manuals User tutorial, Developer manual, Setup manual
Code client server
Deployment Diagram instructions

Not all parts of the deliverables are necessary but the evidence should be convincing of the scope.


Quality

Explain the quality attributes (non functional) of your project deliverables. Have you designed the architecture, use a design pattern, etc? Does your architecture address scalability, performance, reliability, availability, fault tolerance, usability, etc. Does your design address maintainability, flexibility, configurability, etc. Be brief here but you can link to diagrams or code detail pages. Do not repeat the technical complexity part, link to it if necessary.


Deployment

In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a deployment diagram link.


User Testing

Describe the testing done on your system. For example, the number of UAT, tester profile, test cases, survey results, issue tracker, bug reports, etc.

Reflection

Compile common lessons and reflection for the team and for each team member. Be brief.


Team Reflection

Key lessons learned – indicating where the team improved, or would do things differently next time. You may refer to the learning outcome summary in your proposal. A very short checklist style will suffice. It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.


Individual Reflection

Describe in a paragraph, the key areas of learning or improvement. These should be personal areas of growth or learning. Each individual should list his/her effort, responsibility, actual contributions and personal reflection. Do not repeat team project contributions or member roles. Link if necessary.


Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.