HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2011T1 Aperture"

From IS480
Jump to navigation Jump to search
Line 153: Line 153:
 
====Paper Prototype====
 
====Paper Prototype====
 
<div style="margin-bottom:20px;">
 
<div style="margin-bottom:20px;">
[[Media:Aperture-Pivotal.Expert.2-Paper.Prototype.v1.3.pdf|Aperture-Pivotal.Expert.2-Paper.Prototype.v1.3.pdf]]
+
[[Media:Aperture-Pivotal.Expert.2-Paper.Prototype.v1.4.pdf|Aperture-Pivotal.Expert.2-Paper.Prototype.v1.4.pdf]]
 
</div>
 
</div>
  

Revision as of 20:37, 10 August 2011

Pivotalexpert2-aperture-teamstructure-v04-700px.-CCH.dSiGnz-.png



Project Overview

Pivotalexpert2.0-v02-logo-500px.-CCH.dSiGnz-.png


Project Description

Pivotal Expert is a fun social networking platform which helps entrepreneurs turn their ideas into reality, by easily providing them relevant student developers who are looking for opportunities to gain real world developing exposure and vice versa.


Project Goals

The goal for Pivotal Expert 2.0 is to integrate social networking features and provide student developers with a clear list of achievements that they can unlock to improve their personal profiles and increase their technical experience.

Another goal would also be to create a personal Return-on-Time (ROT) view that will help student developers better understand the area in which they are earning the greatest compensation for their time spent on projects.

Finally, the team will develop the features and business model to support the crowd-sourced evangelization and adoption of Pivotal Expert globally.


Learning Outcomes

Learning Lessons
S/N Lessons Description Achievement Methods
1. IT architecture, design and development skills
System requirements specification skills
  • Propose functional and non-functional requirements.
  • Prioritize the requirements.
  • Propose the infrastructure and applications needed to complete this project.
Implementation skills
  • Integrating third party tools such as PayPal and Janrain.
  • Learning Python and Angular.js.
2. Project management skills
Scope management skills
  • Select features from a list of requirements given by the client to implement.
  • Manage changes to requirements.
  • Allocate time and resources for unexpected events.
Risks management skills
  • Define risks and mitigation strategy.
  • Monitor the risks.
  • Execute mitigation strategy where necessary.
Project integration and time management skills
  • Propose the schedule for the project.
  • Develop a Velocity metric to monitor the team’s progress. The velocity score will come from Pivotal Tracker software.
Configuration management skills
  • Use GitHub as a repository for our codes.
Quality management skills
  • Use Selenium IDE and code coverage to test functions and features.
  • Develop test cases for User Acceptance Tests (UATs), and evaluate the feedback.
3. Learning to learn skills
Search skills
  • Search for e-books and resources for third party tools such as PayPal.
4. Collaboration (or team) skills
Skills to improve the effectiveness of group processes and work products
  • Create a culture where team members are honest with one another.
  • Have monthly peer appraisals to allow team members to offer constructive feedback.
5. Communication skills
Presentation skills
  • Present features, project management and team progress to the client.
Writing skills
  • Produce documentation for the project, such as proposal, reports and user manual.
  • Update the wiki with information regarding our project.


Deliverables


Project Management

Project Timeline

Aperture-pivotalexpert2-wiki-timeline-v02.-CCH.dSiGnz--1000px.png

Agile Methodology

  • In progress

Metrics

Velocity Metric

Aperture-pivotalexpert2-wiki-metrics-velocity-v01-800px.jpg
Iteration-Velocity Progress
Iteration
No.
Start
Date
End
Date
No. of
Weeks
Team
Strength
Points Velocity Score
(Pts - Velocity)
1 07/06/2011 13/06/2011 1 0% 0 0 0
2 14/06/2011 20/06/2011 1 0% 0 0 0
3 21/06/2011 27/06/2011 1 0% 0 0 0
4 28/06/2011 04/07/2011 1 60% 6 10 -4
5 05/07/2011 11/07/2011 1 60% 2 10 -8
6 12/07/2011 18/07/2011 1 60% 16 10 6
7 19/07/2011 25/07/2011 1 60% 0 10 -10
8 26/07/2011 01/08/2011 1 60% 11 10 1

Bug Metric

Aperture-pivotalexpert2-wiki-metrics-bug-v02-800px.jpg

Risk Management

Risk Analysis

1.    Scope Risk
Risk Statement Risk Rating
(Derived)
Likelihood
(High/Med/Low)
Impact Level
(High/Med/Low)
Mitigation Strategy Potential Impact of Strategy
  • Dynamic (undefined) requirement list.
B
Medium
Medium
  • Develop paper prototypes to ensure that the client and the team agrees on the outcome.
  • Divide huge tasks into smaller features that can be pushed out on a weekly basis.
  • This will allow involved parties to better understand and adapt quickly to amended ideas.
  • It will also allow the client to check if the team interprets the requirements correctly.
  • Overpromising features to client.
A
Medium
High
  • Prioritize list of features in Pivotal Tracker and get client to confirm.
  • Negotiating the priorities of features allows the team to understand the client's priorities.
  • The client will also be able to see which features can be completed by the end of the project, based on Pivotal Tracker's forecasts
2.    Schedule Risk
Risk Statement Risk Rating
(Derived)
Likelihood
(High/Med/Low)
Impact Level
(High/Med/Low)
Mitigation Strategy Potential Impact of Strategy
  • Different priorities of team members.
C
Medium
Low
  • Communicate and align individual members' priorities and project priorities.
  • Set clear tasks together as a team every week.
  • This will better help complete essential tasks first, in an effort to avoid incurring delays in the overall team schedule.
  • Over-management / Under-management.
C
Low
Medium
  • Conduct honest and objective peer reviews.
  • Have team members to assist the Project Manager in managing the team's progress.
  • This would empower team members to be very comfortable and in-tune with each other and their working styles, which will enable the team to function more efficiently in the long-term.
3.    Resource Risk
Risk Statement Risk Rating
(Derived)
Likelihood
(High/Med/Low)
Impact Level
(High/Med/Low)
Mitigation Strategy Potential Impact of Strategy
  • Unavailability of online service resources such as downtime of Google App Engine (GAE).
A
Medium
High
  • Focus the main bulk of code development on local developer's machine (localhost).
  • Shift the load of site-testing onto online resources, to better capitalize on resource capabilities such as load-testing on Cloud Services.
  • This will deviate the development team's heavy reliance on online service resources, which will minimize delays and enable the continued progress of the project's development despite changing external factors.
  • Overreliance on skilled / experienced team members.
B
Medium
Medium
  • Allocate tasks according to each member's strength and assigned job scope(s).
  • Break down tasks into smaller tasks so that they are more easily manageable.
  • Review individual members' progress during weekly meetings and reassign tasks between members where necessary.
  • This will enable the team to tap on each member's unique abilities and talents, thus maximizing the output potential of the assigned tasks.
  • It will also allow team members to have a work-life balance, and improve on individual skills to work interdependently as a team.
4.    Technical Risk
Risk Statement Risk Rating
(Derived)
Likelihood
(High/Med/Low)
Impact Level
(High/Med/Low)
Mitigation Strategy Potential Impact of Strategy
  • Working with new technology and tools.
A
High
High
  • Plan the project to allow sufficient time for the team to familiarize themselves with new technology and tools.
  • Arrange mini-group learning / sharing sessions, to help improve members' knowledge on new technology and tools.
  • This will allow members to be more comfortable venturing into a new platform or utilizing a new tool for the project.
  • The learning curve will potentially be less steep for members and implementation of new features can be expected over a shorter period of time.
  • Application contains bugs after handover.
A
High
High
  • Have mini-test sessions on different modules of project, especially when a new feature is rolled out.
  • Allocate a few weeks post-development for the lead developer to test and clean up the codes.
  • This will prevent any potential breakdown of the entire website after the handover of the project.

Risk Matrix

Aperture-pivotalexpert2-wiki-riskmatrix-v01-300px.png


Features Delivered

Features Progress List
S/N Feature Status Completed Date
1. Paypal In Progress -
2. GeoIP In Progress -
3. Analytics In Progress -
4. Marketing In Progress -
5. Crowd Sourcing In Progress -


Technical Applications

Collaboration Tools

Technical Tools

Progress Summary

Minutes Repository

Minutes Breakdown

April 2011

Meeting Type Meeting Minutes
Team Meetings
With Supervisor Nil
With Client Nil


May 2011

Meeting Type Meeting Minutes
Team Meetings
With Supervisor Nil
With Client Nil


June 2011

Meeting Type Meeting Minutes
Team Meetings
With Supervisor
With Client Nil


July 2011

Meeting Type Meeting Minutes
Team Meetings
With Supervisor
With Client Nil