HeaderSIS.jpg

IS480 Team wiki: 2017T2 LoLo Final Wiki

From IS480
Jump to navigation Jump to search
LoLo Logo.png

Appsolute Home.png   HOME

Appsolute AboutUs.png   ABOUT US

Appsolute ProjectOverview.png   PROJECT OVERVIEW

Appsolute management.png   PROJECT MANAGEMENT

Appsolute documentation.png   DOCUMENTATION

MAIN WIKI MID TERM WIKI FINAL WIKI

Project Progress Summary

Dashboard-01.PNG Dashboard-f2.PNG Dashboard-f3.PNG Dashboard-f4.PNG

Dashboard Project Desc-05.png


Finals Slides icon.PNG
MediConnect.jpg

Project Highlights

Team LoLo Highlights.png

Project Management

Project Status

TeamLoLo Scope.png



Requirements Specification Finals.png

Project Schedule (Planned vs Actual)

The project plan was adjusted with each individual team member's commitments in mind after acceptance, resulting in some sprints with smaller tasks.

The team has also added estimated release dates into the project plan for better representation. After the Midterms, we implemented UI improvements based on feedback from UAT 2. We also did a release before UAT 3 was conducted so as to allow users to start using the application. We decided to shift the 'Group Messaging' function to a later sprint as the 'Audit' function took a longer duration to implement.

Planned Schedule

Team LoLo Original Timeline.png

Actual Schedule

Timeline 28032017-01.png

Project Metrics

The team is using Sprint Velocity, Sprint Burndown and Bug Metrics to ensure effective planning for our subsequent sprints. Each sprint is reviewed after completion and taken into consideration to gauge the number of tasks / story points the team can complete next sprint.

Sprint Velocity

Team LoLo Sprint Velocity Chart.PNG


The Sprint Velocity Metric shows the amount of value delivered in each sprint, this enables the team to predict the amount of work we can get done in future sprints. It is used mostly during our sprint planning meetings. In each sprint, we sum up the estimated story points for each task the team has committed to do and actually completed. The sprint has improved estimation and hence sprint planning by estimating story points for sub-tasks from Sprint 7 onwards.

Overall Burndown Chart

Product Burndown Chart Finals.PNG

Burndown Chart

Team LoLo Sprint 13 Burndown.png
Sprint 12
Sprint 11
Sprint 10
Sprint 9
Sprint 8
Sprint 7
Sprint 6
Sprint 5
Sprint 4


The Burndown Chart shows the actual and estimated amount of work to be done in a sprint. The horizontal x-axis in a Burndown Chart indicates time, and the vertical y-axis indicates story points (estimated complexity of issues). The team has also included a Product/Overall Burndown Chart to display overall progress.

Team LoLo has observed from the slow progress that we have been planning too optimistically and included it as an important learning point and have made adjustments by planning more realistically, eg. we decreased commitment for Sprint 10 by 27%. Another improvement the team will be adopting will be increased frequency of status updates on task progress to improve the burndown for each sprint.

Bug Metrics

Team LoLo Bug Score.PNG

The Bug Metrics shows how many bugs there are in each sprint. The team has managed to solve every critical bug encountered before the end of every sprint and maintained bug score to be as low as possible.

Project Risks

The team felt that risk 5 and 6 will impact the team the most if it turns into an issue. These two risks did happen and are explained in the diagram below.

Mid Term Risks.PNG
S/N Risk Type Risk Event Likelihood Impact Category Mitigation
1 Technical Risk The team is unfamiliar with project technologies like Spring Framework and Microsoft Azure servers. High Medium Red The team will research and share their findings with the team.
2 Users Inability to find sufficient testers from overseas land High Medium Red Work with sponsor closely in finding overseas medical institutions (both public and private) for testers
3 Project Management Project will be delayed due to wrong estimation Low Medium Green Have constant reviews on our project schedule and effort taken to complete tasks
4 UAT Schedule UAT Dates dependent on availability of testers overseas, causing a variance of 2-3 days. Medium Low Green Maintain regular communication with Sponsor during the period of UAT to ensure smooth execution
5 Scope Expecting more feedback from Sponsor on application after UAT 2 which will result in scope creep if not properly discussed. Medium Medium Yellow The need to stay within scope has been communicated and both the Team and Sponsor understands that an uncompleted, old requirement will be swapped out with a new requirement of equal effort needed.
6 Schedule Might not be able to follow planned timeline and complete "nice-to-haves" due to lower sprint velocity than expected. Medium Medium Yellow Mitigation Plan 1: Schedule should be re-estimated with documentation and deployment efforts. Work closely with sponsor and supervisor during re-scheduling effort.

Mitigation Plan 2: Propose to sponsor to remove nice-to-have Sprint 13 to gain buffer time and address final issues and successful hand-over, gain more time for team’s preparation for final exams.

7 Slow Application Response due to Network Users might not be able to use the application if they are using slow network in the Philippines. Medium High Red Mitigation Plan 1: Resizing/Compressing images and videos.

Mitigation Plan 2: Minify Javascript files.



Technical Complexity

Instant Messaging

Instant Messaging 1.PNG


Instant Messaging 2.PNG


Instant Messaging 3.PNG


Instant Messaging 4.PNG



Add/Edit Course UI

Add Edit UI 1.PNG


Add Edit UI 2.PNG


Add Edit UI 3.PNG


Add Edit UI 4.PNG


Quality of product

Intermediate Deliverables

Topic of Interest Link
Project Management Project Schedule
Metrics
Risk Management
Change Management
Minutes
Project Overview Project Overview
Project Scope
Project Motivation
Project Documentation Use Case Diagram
Technologies Used
Architecture Diagram
Prototype
Testing User Testing

Deployment

You may access our application with the following URLs. You are highly recommended to use the Test Deployment server if you wish to navigate around the application.

Live Deployment: http://www.mediconnect.online/
Test Deployment: http://52.187.125.147/

Testing

TeamLoLo InternalTesting.PNG

Below is a sample of how bugs are documented in the bug log.

TeamLoLo Buglog.PNG



TeamLoLo UAT1 Midterm.png

For more information regarding UAT1, please refer to Team LoLo UAT1

TeamLoLo UAT2 Midterm.png

For more information regarding UAT2, please refer to Team LoLo UAT2

TeamLoLo UAT3 Schedule.PNG

For more information regarding UAT3, please refer to Team LoLo UAT3

TeamLoLo HE Schedule.PNG

For more information regarding Heuristic Evaluation, please refer to Team LoLo Heuristic Evaluation

TeamLoLo NFT1.PNG

Below is a sample of the non-functional testing done.

TeamLoLo NFT.PNG


The team has conducted load testing for the most resource intensive function that the application has. Below are the results of the average page load time and failed request based on the Search Course function from user load of 1 to 1000.
TeamLoLo LoadTesting PageTime.PNG
TeamLoLo LoadTesting FailedRequest.PNG


Reflection

Sponsor's Feedback

"The team have been excellent. I have been continually impressed by their skills, problem solving ability and keenness to support AWH’s mission. The product is looking good, and they are responsive to new requests." - Edward Booty

Team Reflection

Over the course of the project, we have picked up new skills by taking up new roles and trying out technology that we are not familiar with. We also learnt that effective communication and stakeholder management are essential for ensuring that our project is managed well.

Individual Reflection

I have learnt that maintaining constant communications with your stakeholders keeps them in the know and also helps you to re-assess the project's progress every time you have a meeting. This allows me to better manage the project and plan with refined information. - Kar Kit


I have learnt about the importance of stakeholder management due to different expectations and needs each stakeholder has. It is important to strike a balance among them. Have to always be prepared for unexpected events and changes! - Vereen


I learnt the importance of thinking from the users' point of view when developing the User Interface. I also learnt that constant communication with the stakeholders as well as within the team allows us to work more effectively. - Jennifer


I have learnt the importance of developing a reliable, scalable and easy to manage application. Also, the difficulties that we have encountered at the beginning with Spring has proven to be worthwhile, as the framework has helped us to break down big modules into small methods that can be reused. - Brian