HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T1 IPMAN Midterm Wiki"

From IS480
Jump to navigation Jump to search
Line 80: Line 80:
 
<br/>
 
<br/>
 
===<div style="background: #07264C; padding: 15px; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:Garamond"><font color= #FFFFFF>Project Schedule (Plan vs. Actual)</font></div>===
 
===<div style="background: #07264C; padding: 15px; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:Garamond"><font color= #FFFFFF>Project Schedule (Plan vs. Actual)</font></div>===
 +
<div style="font-family:Garamond;font-size:16px">
 +
Several changes were made to the project schedule due to greater emphasis on Smart Marketing module and Dashboard Summary as requested by sponsors. Hence, IPMAN has dropped several tasks that were scheduled in subsequent sprints to focus on these changes (as reflected in the actual schedule). Progress of the team is well-paced and optimistic.
 +
<br/>
 +
</div>
 
===<div style="font-size:16px; font-family:Garamond">Planned Project Schedule===
 
===<div style="font-size:16px; font-family:Garamond">Planned Project Schedule===
 
[[Image:IPMAN Timeline MidTerm Planned.png|center|1100px]]
 
[[Image:IPMAN Timeline MidTerm Planned.png|center|1100px]]
Line 89: Line 93:
 
<br/>
 
<br/>
 
===<div style="background: #07264C; padding: 15px; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:Garamond"><font color= #FFFFFF>Project Risks</font></div>===
 
===<div style="background: #07264C; padding: 15px; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:Garamond"><font color= #FFFFFF>Project Risks</font></div>===
 +
<div style="font-family:Garamond;font-size:16px">
 +
From the period of Acceptance till Mid-Terms, we will like to highlight that our top 2 concerns were 1) Technical Risk and 2) Stakeholder Management Risk as described below:
 +
<br/>
 +
</div>
 +
<center>
 +
{| class="wikitable" style="font-family:Garamond; background-color:#FFFFFF; width: 1000px;" align="center"
 +
|-
 +
 +
! style="color:#ecf0f1; background-color:#07264C;" width="100pt" | Risk Type
 +
! style="color:#ecf0f1; background-color:#07264C;" width="300pt" | Risk Event
 +
! style="color:#ecf0f1; background-color:#07264C;" width="100pt" | Likelihood
 +
! style="color:#ecf0f1; background-color:#07264C;" width="100pt" | Impact Level
 +
! style="color:#ecf0f1; background-color:#07264C;" width="50pt" | Category
 +
! style="color:#ecf0f1; background-color:#07264C;" width="100pt" | Strategy Adopted
 +
! style="color:#ecf0f1; background-color:#07264C;" width="250pt" | Actions
 +
|-
 +
 +
|style="text-align: center;"| Technical Risk
 +
|style="text-align: left;"| Team was unable to deploy as soon as all the bugs were resolved. Whenever sponsors report for bug issues, team immediately resolves the bugs. However, team was unable to deploy the application with the fixed bugs as team was still building on the features in the current sprint and would only deploy the application at the end of the sprint when all features were completed.
 +
|style="text-align: center;"| High
 +
|style="text-align: center;"| High
 +
|style="text-align: center;"| A
 +
|style="text-align: center;"| Mitigate
 +
|style="text-align: left;"| Team came out with another branch for deployment which means there are now 2 branches, one of it is the deployment branch and another branch is to work on the existing features. Therefore, whenever sponsor raises any bug, team would be able to resolve the bugs and deploy immediately without waiting for the features to be completed at the end of the sprint.
 +
|-
 +
 +
|style="text-align: center;"| Stakeholder Management Risk
 +
|style="text-align: left;"|Team had to manage not only sponsors but also the developer team that the sponsors engaged. For instance, the freelancer developers had built Intercom to track the customers’ interaction on the application without us knowing. This feature implemented affected the Smart Marketing features that we built.
 +
|style="text-align: center;"| High
 +
|style="text-align: center;"| High
 +
|style="text-align: center;"| A
 +
|style="text-align: center;"| Mitigate
 +
|style="text-align: left;"| Team communicated with sponsors and found out more the implementation of Intercom. Team also constantly met up with sponsor and checked with him about the progress of Intercom. Team came out with a communication protocol between the sponsors, developer team and team. Team is using Trello and Telegram for communications and updates.
 +
|}
 +
</center>
 
<br/>
 
<br/>
 +
 
===<div style="background: #07264C; padding: 15px; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:Garamond"><font color= #FFFFFF>Technical Complexity</font></div>===
 
===<div style="background: #07264C; padding: 15px; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:Garamond"><font color= #FFFFFF>Technical Complexity</font></div>===
 
<br/>
 
<br/>

Revision as of 21:53, 28 September 2016

Team IPMAN Logo 1200x960.png


Team IPMAN Icon Home.png   HOME

 

Team IPMAN Icon AboutUs.png   ABOUT US

 

Team IPMAN Icon ProjectOverview.png   PROJECT OVERVIEW

 

Team IPMAN Icon ProjectManagement.png   PROJECT MANAGEMENT

 

Team IPMAN Icon ProjectDocumentation.png   DOCUMENTATION

 


IPMAN MidTermWiki Title.png



Project Progress Summary


IPMAN Dashboard MidTerm.png

IPMAN MidTermSlides Icon.png IPMAN MidTermDeployedSite Icon.png

Project Highlights

  • Implementation of Facebook Login, due to unfamiliarity, we took 2 weeks to learn and implement this function in Iteration 3
  • Integration with QR code implemented by sponsors so that labels can be pre-populated once code is scanned in Iteration 5
  • Conducted our first UAT with our sponsors and packers in Iteration 6 to test our process order and customer management module and worked on Performance and Design Improvements in Iteration 6
  • Decision made in Iteration 7 to shift several tasks for subsequent iterations due to greater focus on smart marketing and dashboard summary as requested by sponsor. Dropped Facebook bot and recommendation engine (planned for iteration 12) so that we could spend more time on these two modules.
  • Conducted our second UAT with our sponsors and their business development in-charge in Iteration 9 to provide feedback mainly on our smart marketing module
  • Integration of Intercom together with our system in Iteration 10


Project Management


Project Status

IPMAN Progress Overview Midterm.png

Access the detailed progress of functionalities here: IPMAN Functionalities Progress List

Project Schedule (Plan vs. Actual)

Several changes were made to the project schedule due to greater emphasis on Smart Marketing module and Dashboard Summary as requested by sponsors. Hence, IPMAN has dropped several tasks that were scheduled in subsequent sprints to focus on these changes (as reflected in the actual schedule). Progress of the team is well-paced and optimistic.

Planned Project Schedule

IPMAN Timeline MidTerm Planned.png


Actual Project Schedule

IPMAN Timeline MidTerm Actual.png


Project Metrics


Project Risks

From the period of Acceptance till Mid-Terms, we will like to highlight that our top 2 concerns were 1) Technical Risk and 2) Stakeholder Management Risk as described below:

Risk Type Risk Event Likelihood Impact Level Category Strategy Adopted Actions
Technical Risk Team was unable to deploy as soon as all the bugs were resolved. Whenever sponsors report for bug issues, team immediately resolves the bugs. However, team was unable to deploy the application with the fixed bugs as team was still building on the features in the current sprint and would only deploy the application at the end of the sprint when all features were completed. High High A Mitigate Team came out with another branch for deployment which means there are now 2 branches, one of it is the deployment branch and another branch is to work on the existing features. Therefore, whenever sponsor raises any bug, team would be able to resolve the bugs and deploy immediately without waiting for the features to be completed at the end of the sprint.
Stakeholder Management Risk Team had to manage not only sponsors but also the developer team that the sponsors engaged. For instance, the freelancer developers had built Intercom to track the customers’ interaction on the application without us knowing. This feature implemented affected the Smart Marketing features that we built. High High A Mitigate Team communicated with sponsors and found out more the implementation of Intercom. Team also constantly met up with sponsor and checked with him about the progress of Intercom. Team came out with a communication protocol between the sponsors, developer team and team. Team is using Trello and Telegram for communications and updates.


Technical Complexity



Quality of Product


Intermediate Deliverables

Topic of Interest Link
Project Management Project Schedule
User Stories
Minutes
Metrics
Risk Management
Change Management
Project Overview Project Overview
Team's Motivation
Project Scope
Project Documentation Personas & Scenarios
Diagrams
Technologies Implemented
Low & Mid Fidelity Prototypes
Testing Testing Documentation


Deployment


Testing



Reflection


Team Reflection

This journey has proven to be an enriching learning process for Team IPMAN. We have learnt immensely from one another's strengths and weaknesses and were able to proficiently complement our different working styles. We have also learnt that communication, compromise and active participation is key to ensure a collaborative learning environment. In addition, together with our generous sponsors who have provided the flexibility and autonomy to work with real data, we have enjoyed working on this project.

Individual Reflections



Silhouettes wiki background IPMAN.png