HeaderSIS.jpg

IS480 Team wiki: 2011T1 Aperture - Midterm Wiki

From IS480
Jump to navigation Jump to search
Pivotalexpert2-aperture-midtermwiki-header-v02-700px.jpg





Project Progress Summary

Progress Description

Our team has progressed slowly but steadily since our acceptance. We encountered a major obstacle, which is the creating of a live PayPal account for Pivotal Experts. They required us to have a working live application for them to verify before they allow us to create a live PayPal account. So we had to delay our PayPal task until we can complete the basic functionalities. We are confident of getting 70% of the basic functionality live by midterm. Although this is behind the schedule we planned during proposal, which was caused by the underestimation of the duration and complexity of the tasks, we are confident of completing 70% of the additional features on top of the basic functionalities, by the end of the term.

Project Highlights

What unexpected events occurred?

  • PayPal required us to have a live application before allowing us to create a live PayPal account
  • Project Management
    • The front end team took 7 weeks to learn Angular JS, which was much longer than expected. On top of that, they needed to learn Javascript, which we did not allocate time for.
    • Team members had a higher workload than expected
    • Task durations were underestimated (Points allocated to each task in Pivotal Tracker)


Project Management

Project Status

Highlight changes to modules, the completion status (implemented, UAT done, client approved, deployed, etc), the confidence level (0-1 where 0 is no confident of getting it done, 1 is 100% confident in getting it done) and comments (who has been assigned to do it, new scope, removed scoped, etc). Please use a table format to summarize with links to function details.

Task / Function / Features Status Confident Level (0-1) Task Owner
PayPal 50% 1 Daniel
Login/logout 100% 1 Daniel
View Dashboard 100% 1 Daniel
Edit Profile 100% 1
Create/Edit Project 100% 1
View Projects 100% 1
View Project Bids 100% 1
Create Bid 100% 1
View Workroom 100% 1
Send Messages 50% 1
Accept/Reject Bid 0% 1
Accept/Reject Deliverable 0% 1
Post Comments in Workroom 0% 1
Edit Iteration Plan 0% 1
Search for Project 0% 1
Email Verification 0% 1
Sort/Filter Projects 0% 1
Sort/Filter Developers 0% 1
Receive Email 0% 1
Submit Feedback 0% 1
Negotiate Pay Raise 0% 1
Integrate Singpath Badges 0% 1
Social Networking 0% 1
Crowdsourcing 0% 1
Location Identification 0% 1
View Google Analytics 0% 1
Submit/View Return On Time 0% 1
View Pivotal Expert Analytics 0% 1
View Advertising Recommendations 0% 1

Project Schedule (Plan Vs Actual)

Highlight changes to modules, the completion status (implemented, UAT done, client approved, deployed, etc), the confidence level (0-1 where 0 is no confident of getting it done, 1 is 100% confident in getting it done) and comments (who has been assigned to do it, new scope, removed scoped, etc). Please use a table format to summarize with links to function details.

Iteration Features Planned Actual Comments
1. TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT
TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT
TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT
2. TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT
TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT
TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT

Project Metrics

Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.

Project Risks

Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken.

Risk Probability Impact Mitigation
Completing all the additional functionalities, on top of the basic functionalities High High - Re-allocate manpower to help speed up development process

- Using the team's average velocity in Pivotal Tracker, gauge the number of functionalities able to be completed, and inform client of functionalities which cannot be completed

PayPal implementation Low High Complete the basic functionalities required for payments and deploy the application to live server for PayPal to verify before they approve Pivotal Expert's live PayPal account.
Over-management / Under-management Low Medium Have team members to assist the Project Manager in managing the team's progress.


Be sure to prioritize the risks.

Technical Complexity

1. Utilizing two different programming languages - Javascript using AngularJS for views, and Python for the models and controllers.
2. Implementing PayPal payments.
3. Implementing a REST server on Google App Engine.

Quality of Product

Quality Achieved

Developed the application such that the views can be tested and run independently of the database models. This is achieved through the use of Angular JS, which is a Javascript MVC framework. Anyone can just take the views out and run them on their computer, without any web server required. The data will be stored in static JSON files within the folder.

Intermediate Deliverables

There should be some evidence of work in progress.

S/N Stage Specification Modules
1. Project Management Minutes Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7
Metrics <<Velocity metrics>>, <<Bug metrics>>
2. Requirements List of functionalities <<priority list>>
3. Analysis Use case <<Use Case Diagram>>, <<Use Case Description>>
4. Testing UAT test plan In Progress


Not all parts of the deliverables are necessary but the evidence should be convincing of the progress. Try to include design deliverables that shows the quality of your project.

Deployment

In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a deployment diagram link.

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

Our Thoughts

In this section, describe what have the team learn? Be brief. Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.


Team Reflection

Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.

Individual Reflection

You may include individual reflection if that make sense at this point. The team is uncooperative and did not follow my instructions.