HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 253: Line 253:
  
 
Since the solution requires the implementation of skills that were not taught in SMU, the team has settled down and learnt the skills together so that every member will understand and be able to use it in future when needed. It was hard for the team at first to have a common timeslot just to learn the new skills, but we are glad that the efforts are worth it as everyone is now equipped with the same skills and has been able to assist the weaker members during the development process.
 
Since the solution requires the implementation of skills that were not taught in SMU, the team has settled down and learnt the skills together so that every member will understand and be able to use it in future when needed. It was hard for the team at first to have a common timeslot just to learn the new skills, but we are glad that the efforts are worth it as everyone is now equipped with the same skills and has been able to assist the weaker members during the development process.
 
 
   
 
   
 
'''Importance of User Testing'''
 
'''Importance of User Testing'''

Revision as of 17:37, 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.

RUP.jpg

Construction Phase

Planned Construction.jpg

Plan vs Actual Construction Phase(6B)

Planned 6B.jpg Actual 6B.jpg

Plan vs Actual Transition Phase

Planned Transition.jpg Actual Transition.jpg

Project Metrics

Schedule 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.

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.

Bug Metrics

The team has also implemented the use of Bug Metrics that is used to determine the values / number of bugs that arise during the development process, and is possible to affect the entire project. With the bug metrics, the developers and team are able to know what necessary actions need to be taken in order to ensure that the whole project runs smoothly and according to the planned schedule.

Bug Metric 1.jpg

Bug Metric 2.jpg

The team is pleased that despite an extended development process as compared to the other groups, there has been minimal bugs arising during the process and hence, does not affect the team's project schedule. In a way, bug metric has helped the team to be more careful in preventing bugs from occuring, which will eventually affect the team's progress on tasks or functions that need to be done.

Project Risks & Mitigations

Risks 2.jpg

Risks 1.jpg

Throughout the entire project, the team has learnt that there are risks in every project and the risks encountered are similar yet different as compared to other groups and it is important to come out with mitigation strategies to solve these risks and prevent any possible delays in the project schedule.

The greatest risk faced by the team is in the area of technology. As the technology used by the client has not been learnt by the team, there is a steep learning curve for the team to be able to understand the technology in the shortest possible time in order to ensure that the entire development process using this technology is smooth. To tackle this issue, the team has created additional buffer time in the project schedule for the learning of technology, as well as looking through discussion forums and online tutorials in order to have hands-on experience and better knowledge. These skills have equipped the team with the ability to learn new skills yet at the same time, putting the technology learnt into possible use during the entire project progress.

Technical Complexity

Quality of Product

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

Deployment

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

These are the lessons and skills that the team has learnt throughout the entire project.

Types Description
Project Management
  • How to communicate effectively with all stakeholders
  • How to determine the most efficient project schedule
  • Allocation of responsibilities based on individual capabilities
  • Tracking of project progress
  • Priortising tasks
  • Determine possible risks and mitigation strategies
  • Planning for User Testing
Technical Skills
  • Gathering user requirements
  • Use of new technology such as Webdrive, LinQ and Github
  • Windows Service Development
  • Creating a web application for a more efficient process
  • Using Log4Net to track errors occurred in windows service

Team Reflection

Reaching a common agreement

With the different schedule that all team members have, it is tough for the team to have a consensus on the meeting dates to get the tasks and functions done. Despite this, the team has been trying our best in re-scheduling other appointments or tasks for a weekly meeting within the team, and with the client and supervisor. We spent countless numbers of hours discussing and reviewing the available dates where all of us are agreeable and convenient in doing our best for the project.

Importance of understanding the entire business process

Since the solution will be deployed in real-life, it is important for the team to understand fully on how ESPN conducts its video uploading process in ensuring that the automated solution will be able to fill in all gaps. The team has spent countless meetings at the client's place to have a demostration and ask questions that will be related to the end-product. The team is now confident of explaining the entire process and how the solution will further enhance the existing process.

Learning new skills together

Since the solution requires the implementation of skills that were not taught in SMU, the team has settled down and learnt the skills together so that every member will understand and be able to use it in future when needed. It was hard for the team at first to have a common timeslot just to learn the new skills, but we are glad that the efforts are worth it as everyone is now equipped with the same skills and has been able to assist the weaker members during the development process.

Importance of User Testing

User testing has allowed the team to know the areas of improvements for both the web application and windows service as we are able to have a clearer view of what the end-users are looking at and how the solution is able to help them. A clean user-interface together with a documented user manual helps to make it easier for the end-users when using the system. The team has also obtained feedback from them and made improvements or adjustments based on the potential issues that the first-time end-users face in order to ensure that the system is doing it's best in assisting them and improving their business process.

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.