HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T2 box.us Project Management"

From IS480
Jump to navigation Jump to search
Line 219: Line 219:
  
 
<font color="red">'''UNDER CONSTRUCTION'''</font>
 
<font color="red">'''UNDER CONSTRUCTION'''</font>
[[Image:Milestones_v2_PNG.png | thumb | center | 1000px | Our Project Milestone ]]
+
[[Image:Milestones_v2_PNG.png | thumb | center | 100px | Our Project Milestone ]]
  
 
'''Project Milestones''' - Detailed Project Milestones with their dates can be found at: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=24 Project Milestones List]
 
'''Project Milestones''' - Detailed Project Milestones with their dates can be found at: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=24 Project Milestones List]

Revision as of 00:17, 25 October 2012


Teamphotowiki.jpg

Home Stakeholders Project Overview Project Management Documentation Learning Outcomes Useful Links

Team Box.us is a project team that consists of 6 individuals with varying (and complementing skillsets). The team set out with the following beliefs to achieve at the end of the project:

  • Create value for organizations - Value could be business value and also social value to our sponsors.
  • Sustainable implementations - Our team believes in having projects that would be sustainable and be able to bring value to the organizations in a long run
  • Team Learning - Our team believes in learning during the entire development process so that the experience would be enriching for the organization, the team and the individuals invovled.


Modules Module Name Scope details

  BASIC FEATURES

Manage Account

All Users

  • Account creation to login and access the application
  • View and edit their own account details
  • Empact has ability to accept or reject a volunteer

Manage Profile

All Users

  • Edit profile details

Empact

  • View NPOs and volunteers' profile details

NPO

  • Fill their company profile

Volunteer

  • Fill up a questionnaire to determine the kind of cause they can do, which will then be used as profile
  • View NPOs' profile details

  CORE FEATURES

Manage Task

All Users

  • View available tasks

Empact

  • View list of assignments submitted by NGOs
  • Create, edit, remove tasks based on the assignment which NPOs give
  • Automated matching of tasks and volunteers based on skillsets
  • Send task request to volunteers. The notification will be send via email and push notification(iOS)
  • View applications from volunteers
  • Accept or reject volunteers' task application
  • Update profress details

NGO

  • Post assignment to Empact

Volunteer

  • Apply for task from the list of available tasks
  • Accept or reject task requests from Empact

Manage Task Review

Empact

  • Add, edit remove reviewer to task
  • Approve/reject task completion
  • View Documents

Manage Questions

All Users

  • View all questions
  • Search questions based on keywords

NPO

  • Create, edit, remove question
  • Mark a reply as answer

Volunteer

  • Reply question

Manage Search

All Users

  • Search for task by skillset or causes
  • Set filters to search for NPO

Empact

  • View search result for Empact (ability to send task request)

NPO

  • View search results (no action)

Volunteer

  • View search results (ability to apply for task)

  Value-Enhancing FEATURES

Statistical Reporting

Empact

  • View Statistics
  • Export Statistics
  • View data

Manage Records

Empact

  • View volunteering records
  • Generate records

iPhone Application

iOS Development

Volunteers

  • Be notified of task posting via push notification
  • Accept or reject task offering
  • View questions asked by NGOs
  • Post answers to questions
  • View and search for available task

CONCEPTUALIZATION (07/10/2012 - 27/10/2012)

Conceptualization.jpg


DEVELOPMENT (28/10/2012 - 17/02/2013)

Development.jpg


DEPLOYMENT (18/02/2013 - 31/03/2013)

Deployment Process Boxus.jpg

UNDER CONSTRUCTION

Error creating thumbnail: File with dimensions greater than 12.5 MP
Our Project Milestone

Project Milestones - Detailed Project Milestones with their dates can be found at: Project Milestones List

Project Schedule - Project Schedule on Google Docs

OBJECTIVE

  • To ensure that all project tasks are completed on time and milestones are met.
CALCULATION:

Schedule Ratio = Actual Time / Planned Time

Schedule Ratio Description Response
> 0.8 Team is ahead of schedule Proceed to embark on the next task if possible
0.8 - 1.2 Within healthy schedule range No actions required for ratio above 1.
Keep close monitor on tasks that have a ratio of less than one.
< 1.2 Team is behind schedule Team is behind schedule. Project Manager identifies root cause and allocate more time to complete tasks in the next iteration.


OBJECTIVE

  • To minimize the number of bugs that surface during the duration of a sprint and thus ensuring the quality of the application.
  • A bug is defined as errors in code that causes system to behave differently from expected.


CALCULATION:

Bug Score = (2 X Total No. of Low Severity) + (4 X Total No. of Medium Severity Bug) + (8 X Total No. of High Severity Bug)


Severity Score Severity Level Description
2 LOW Errors that lies with user interface. Features can still work, but not as what is expected.
4 MEDIUM Errors that prevent an entire feature from working
10 HIGH Errors that prevent more than 1 feature from working
Bug Score Action Plan
6 and below Developers resolve issues within the iteration
7 - 9 Schedule debugging in the buffer of the iteration.
10 and above Priority goes to resolving bug. Project Manager reallocates task for debugging team to focus on debugging.

Sponsor Sourcing

Before everything, we have to find a sponsor. Learning from our past experiences, the team has developed a guideline for sourcing the sponsor. The guidelines are as such:

  • The Motivation: What is the need?
  • The Idea: In short, what is the idea about?
  • The Solution: How would the idea help to solve the need
  • The Scope: What is the focus of the project? The differentiating factor? The X-Factor of the project?
  • The Implementation: Do we have the technical ability to deal with the project?

At the end of this iteration, the team would have a clear idea of what the scope of the project is about and the high-level steps of what needs to be done to get there.


Agile Development

It's all about agility. Our team aims to mimic as close as possible to real-world software engineering experiences. As such, our team has decided to adopt the Agile Development Process that is flexible and meaningful for the entire team. In our Development phase, we iterate between design, build, test and release for each iteration.

There are few sources of change for the project itself. Depending on the initiator of the project change, change control processes would have to be taken into consideration.

TYPES OF CHANGE

Requirement Change

Requirement changes are modifications, additions, deletions of requirements stated in the latest version of requirements documentation. In this case, sponsor and supervisor would be noted. Response from supervisor and sponsor would be sought before decision is sealed.

System Design Change

System changes are modification, additions, deletions to the system architecture and detail system design as stated in the latest versions of system architectural documentations and technical infrastructure documentations. Depending on severity, response from supervisor might be sought before decision is sealed.

Team Process Change

Team Process changes are modifications, additions, deletions to the existing team processes as stated in the latest versions of project management plan and software configuration management plan. In this case, supervisor. Supervisor would be informed.


CHANGE PROCESS

Following the feedback given by our supervisor, we have come up with the revised change process:

  1. Change initiated by external party
  2. Project Manager informed of change
  3. Project Manager makes decision of change and decides if team meeting is needed
  4. Project Manager informs team supervisor and sponsor(only if necessary)
  5. If team meeting is needed, meeting is scheduled, else team would be informed of change once decision made
  6. Change decision is being made known to supervisor
  7. Change implemented and decision is made known to team, supervisor and sponsor(if necessary)


DOCUMENTING CHANGE

Changes that are formalized and agreed upon by team, and stakeholders if necessary, would be recorded in the respective documentation by Project Manager, Deputy Project Manager or Business Analyst. Followup actions of changes made to project and team would be tracked by the Deputy Project Manager.

Our team's risk management approach is in constant monitoring and reviewing risk at the start and end of each milestone.

Risk matrix.gif
No Type Risk Consequence Likelihood Impact Level Risk Assessment Level Mitigation Strategy
1

Business

Unfamiliarity with mobile development frameworks required for the project

  • Inability to make decision about best framework to use
  • Slow project progress because of unfamiliarity

Likely

Major

High

  • Conduct research on possible mobile development technologies and consult peers and supervisors for advice on which framework to use, in view of mobile app's scope
  • Development of mobile application in parallel with web application to highlight any possible loopholes and to buffer for any major changes needed early.
2

Team

Group members making assumptions of technical scope required within the project

Inaccurate estimates of time required to complete tasks that leads to unreliable project deadlines and milestones

Possible

Moderate

High

  • Lay down milestones, deadlines and tasks to do with team before the start of every iteration and review estimates together as a team
  • Project Maanger to actively manage the overrun of schedule through tracking of metrics
3

Business

Difference in understanding of terminologies and terms used in describing the business process (e.g. task, questions, assignments)

Confusion over terms that may lead to the wrong picture being conveyed between client and team

Possible

Minor

Medium

  • Implement a project dictionary where common terms of use are being recorded down
  • Proactive logging down of common terms of use in the project dictionary
4

Project

Change in volunteer matching business process during the development of the system

Decrease in value of system brought to the business.

Possible

Major

High

  • Analyse client's As-Is Process and verify with client about current As-Is Model
  • Consider longevity of the system during the design of system
5

Resources

Multiple users working on the same files resulting in conflicting versions of documentation

Loss of information or mismatch in understanding

Likely

Minor

Minor

  • Segregating editing responsibilities - Business Team to edit business related documents while Technical Team to edit technical-related documents
  • Use of Subversion during the committing of code. Lead Developer would be responsible for any code conflicts.
6

Resources

Hardware and software failure during the development of the project.

  • Failure of hardware would cause latest work that is being developed to be lost.
  • Redundancy and repetition of work is necessary in order to keep up to the pace that is being set by the schedule in the event of a software and hardware failure.

Unlikely

Moderate

Moderate

  • Save development codes onto Subversion
  • Business Analyst to do a weekly backup of all documents and source code.
7

Team

Different workloads and committment in team due to varying workloads and outside commitments

Inaccurate allocation and expectation of team and project manager upon each team member, obstructing accurate time estimation and affects schedule allocation. Unhappiness in team due to unfair work allocations throughout the entire project

Likely

Major

High

  • Set expectations instead of micro-managing how work would be done by individuals
  • Schedule shorter iterations to ensure that targets are met and not piled up.
  • Allocate common coding sessions to allow team to ensure accountability and transparency
8

Business

Misunderstanding of technical requirements between client and project team as clients are not technically-inclined

Re-doing of development work as a result of mismatched expectations between different parties, leading to time wastage

Likely

Severe

High

  • Conduct requirements clarifications before the start of every iteration between team and client to clarify the requirements
  • Using process flow diagrams and storyboards to communicate features with client and team.
  • Discuss about feature design before each development session
  • Recommend and propose technical requirements to client