HeaderSIS.jpg

WRESSENCE Schedule Metric

From IS480
Jump to navigation Jump to search

Back to WRESSENCE PROJECT MANAGEMENT PAGE

Team WRESSENCE
Project Management

Schedule Metric

Definition of Schedule

Schedule is an overview of effort for doing all tasks allocated in terms of hours and days.


The Purpose

Schedule metric serves as a tool to help the team keeps track whether technical development tasks are on on schedule. It also provides a mean to attain better
accuracy in schedule estimation of technical development-related tasks.


Frequency of Measurement

The schedule metric will be updated after completion of each task. The Index will be calculated after each iteration.


The Formula

Index = Actual days used for task completion / Estimated days scheduled for task completion


The Schedule Log


No. Task Description Actual Days Estimated Days Index Impact Level Remarks
01 Plan and design User Interface for Apha Version Development 6 3 2 Critical Lack of systematic process in gathering design feedbacks from members. SOP in gathering design feedbacks is established.
02 Develop User Account Login (ASP.NET Membership) 2 2 1 Neutral Delay due to delay in UI design task. No action needed to be taken.
03 Develop User Account Login (Twitter) 4 3 1.33 High Delay due to delay in UI design task. Urgent meeting is held to re-allocated task ownerships.
04 Develop Calendar Database architecture 1 2 0.5 High Delay due to delay in UI design task. Urgent meeting is held to re-allocated task ownerships so able to complete within shorter time.
05 Develop New User Account Creation (ASP.NET) 1 2 0.5 High Delay due to delay in UI design task. Urgent meeting is held to re-allocated task ownerships so able to complete within shorter time.
06 Develop User Account Login (Facebook) 2 3 0.67 High Delay due to delay in UI design task. Urgent meeting is held to re-allocated task ownerships so able to complete within shorter time.
07 Develop New User Account Creation (Twitter) 2 2 1 Neutral Delay due to delay in UI design task. No action needed to be taken.
08 Develop User Account Login (Google ID) 2 3 0.67 High Delay due to delay in UI design task. Urgent meeting is held to re-allocated task ownerships so able to complete within shorter time.
09 Develop New User Account Creation (Facebook) 3 3 1 Neutral Delay due to delay in UI design task. No action needed to be taken.
10 Develop New User Account Creation (Google ID) 2 5 0.4 High Delay due to delay in UI design task. Urgent meeting is held to re-allocated task ownerships so able to complete within shorter time.
11 Conversion of ASP.NET User Login PSD images into HTML5 2 2 1 Neutral Delay due to delay in UI design task. No action needed to be taken.
12 Set up temporary DNS 1 1 1 Neutral Delay due to delay in UI design task. No action needed to be taken.
13 Set up DNS and IP for Community Site 1 1 1 Neutral Delay due to delay in UI design task. No action needed to be taken.
14 Conversion of Facebook User Login PSD images into HTML5 3 2 1.5 High Delay due to delay in UI design task. Urgent meeting is held to re-allocated task ownerships.
15 Conversion of Twitter User Login PSD images into HTML5 2 2 1 Neutral Good estimation. No action needed to be taken.
16 Conversion of Google User Login PSD images into HTML5 2 2 1 Neutral Good estimation. No action needed to be taken.
17 Test developed functionalities with test cases 2 3 0.67 High Delay due to delay in UI design task. Urgent meeting is held to re-allocated task ownerships so able to complete within shorter time.
18 Debug developed functionalities 5 3 1.67 Critical Delay due to delay in UI design task. Urgent meeting is held to complete task as a team.
Index for Iteration 1: 0.98 (NEUTRAL IMPACT LEVEL)
19 Plan and design User Interface for Beta 1 Version Development 5 5 1 Neutral Good estimation. No action needed to be taken.
20 Revise Application Architecture Design 1 1 1 Neutral Good estimation. No action needed to be taken.
21 Refine Password Validation for Account Creation (ASP.NET) 3 2 1.5 High Delay in completion of task due to underestimation of task complexity. Team meeting is held to better allocate task ownership for future similar tasks.
22 Develop Calendar Auto UI Code Generation 3 3 1 Neutral Good estimation. No action needed to be taken.
23 Develop Calendar Date Calculation 2 2 1 Neutral Good estimation. No action needed to be taken.
24 Linking/Unlinking between all account logins 4 3 1.33 High Delay in completion of task due to underestimation of task complexity. Team meeting is held to better allocate task ownership for future similar tasks.
25 Develop Dates/Weeks Switch 3 3 1 Neutral Good estimation. No action needed to be taken.
26 Develop HTML-based code (Week View) 3 3 1 Neutral Good estimation. No action needed to be taken.
27 Develop Event Pop-Ups 4 3 1.33 High Delay in completion of task due to underestimation of task complexity. Team meeting is held to better allocate task ownership for future similar tasks.
28 Develop Widget Calendar 4 3 1.33 High Delay in completion of task due to underestimation of task complexity. Team meeting is held to better allocate task ownership for future similar tasks.
29 Develop HTML-based code (Pop-up) 4 3 1.33 High Delay in completion of task due to underestimation of task complexity. Team meeting is held to better allocate task ownership for future similar tasks.
30 Connecting Database 2 3 0.67 High Delay in starting task. Task owner worked overtime so able to complete within shorter time.
31 Develop Week and Day View 3 3 1 Neutral Good estimation. No action needed to be taken.
32 Test developed functionalities with test cases 1 1 1 Neutral Delay in starting task due to wrong estimation of previous tasks. Testing task is divided among the team.
33 Debug developed functionalities 2 3 0.67 High Delay in starting task. Task owner worked overtime so able to complete within shorter time.
34 Deployment to virtualized development server 1 1 1 Neutral Delay in starting task due to late testing. Need to improve estimation in task duration.
35 Test and debug on virtualized development server 2 2 1 Neutral Delay in starting task due to wrong estimation of previous tasks. Need to improve estimation in task duration.
36 Deployment to server 1 2 0.5 High Delay in starting task. Task owner worked overtime so able to complete within shorter time.
Index for Iteration 2: 1.04 (NEUTRAL IMPACT LEVEL)
37 Develop Month View 2 2 1 Neutral Good estimation. No action needed to be taken.
38 Revise Application Architecture Design 1 1 1 Neutral Good estimation. No action needed to be taken.
39 Refine event pop up feature 4 3 1.33 High Delay due to UI compatible issues. Discuss as a team to solve.
40 Re-structure Day View/Week View 4 3 1.33 High Met with calendar render issues. Pair team members up for the remaining task completion.
41 Plan and design User Interface for Beta 2 Version Development (Location-based services) 5 5 1 Neutral Good estimation. No action needed to be taken.
42 Integration of all functionalities 1 2 0.5 High UI layout keep having problems when integrating. Pair team members up to solve together.
43 Test functionalities with test cases 1 1 1 Neutral Good estimation. No action needed to be taken.
44 Debug and Deploy to server 2 2 1 Neutral Good estimation. No action needed to be taken.
45 Testing on Deployment server 1 1 1 Neutral Good estimation. No action needed to be taken.
46 Debug and deploy to server 2 1 2 Critical Discovered critical bugs that delay deploy task.
47 Conceptralize Architecture of system 1 1 1 Neutral Good estimation. No action needed to be taken.
48 Develop Location Suggestion (Google) 3 2 1.5 High Inconsistency with results returned. Pair team members up to complete task.
49 Develop Create Review & Read Review 3 3 1 Neutral Good estimation. No action needed to be taken.
50 Integration of all functionalities 1 1 1 Neutral Good estimation. No action needed to be taken.
51 Debug and deploy developed functionalities 3 4 0.75 Neutral Good estimation. No action needed to be taken.
52 Test developed functionalities with test cases 1 1 1 Neutral Good estimation. No action needed to be taken.
53 Debug developed functionalities 2 2 1 Neutral Good estimation. No action needed to be taken.
54 Deployment to server 1 1 1 Neutral Good estimation. No action needed to be taken.
55 Refine Application based on feedbacks 5 4 1.25 High Bugs discovered were more than expected thus required more time to solve.
Index for Iteration 3: 1.08 ( NEUTRAL IMPACT LEVEL)
56 Conceptualize architecture for features of Iteration 4 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
57 Design and Develop Presentation layer for Beta 4 Version Development (Include Error page) 4 4 1 Neutral Progress is good. Good estimation. No action needed to be taken.
58 Develop Quick Add Event 2 2 1 Neutral Progress is good. Good estimation. No action needed to be taken.
59 Develop Time Zone Setting 2 2 1 Neutral Progress is good. Good estimation. No action needed to be taken.
60 Develop Social Media Platform Postings (Facebook and Twitter) 3 3 1 Neutral Progress is good. Good estimation. No action needed to be taken.
61 Develop direction feature (Venue Suggestion) 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
62 Develop Event Reminder 5 2 2.5 Critical Delay due to late starting on task. Worked overtime to complete task within shorter time.
63 Develop Photostream (Write Reviews) 3 2 1.5 High Delay due to modal pop-up issues. Pair team members up to solve the issues.
64 Develop Mini Calendar (Side Panel) 2 2 1 Neutral Progress is good. Good estimation. No action needed to be taken.
65 Test developed functionalities 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
66 Debug developed functionalities 3 2 1.5 High Encounter bug related to displaying directions. Solve bug as a team.
67 Deployment to server 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
68 Test on deployed version and debug 3 3 1 Neutral Progress is good. Good estimation. No action needed to be taken.
69 Deployment to server 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
Index for Iteration 4: 1.18 (NEUTRAL IMPACT LEVEL)
70 Conceptualize architecture for features for Beta Launch 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
71 Plan and design User Interface for Iteration 5 Development 3 4 0.75 Neutral Progress is good. Good estimation. No action needed to be taken.
72 Develop Event Labels 2 3 0.67 High Change in labeling concept. Additional time used to re-design and develop the feature.
73 Develop Import Birthdays 3 3 1 Neutral Progress is good. Good estimation. No action needed to be taken.
74 Develop Public Feeds/Events 3 3 1 Neutral Progress is good. Good estimation. No action needed to be taken.
75 Set up Beta Help Messenger (Zopim) 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
76 Test developed functionalities 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
77 Debug developed functionalities 4 3 1.33 High Inconsistency in functions' behaviours (LBS). Team stopped tasks on-hands to tackle the issue.
78 Deployment to server 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
79 Test on deployed version and debug 4 2 2 Critical Major bugs found. Team stopped tasks on-hands and solve bugs as a team.
80 Deployment to server 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
Index for Iteration 5: 1.04 (NEUTRAL IMPACT LEVEL)
81 Refine based on consolidated feedbacks from Beta 5 3 1.67 Critical New feature needed to be implemented and duration is wrongly estimated.
82 Test and Debug application 3 3 1 Neutral Progress is good. Good estimation. No action needed to be taken.
83 Deployment to server 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
84 Plan and design User Interface for Final Development 1 2 0.5 High Delay as design needed to be re-considered and refined.
85 Conceptualize architecture for features of Iteration 6 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
86 Develop External Calendar Import 2 2 1 Neutral Progress is good. Good estimation. No action needed to be taken.
87 Test developed functionalities 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
88 Debug developed functionalities 3 3 1 Neutral Progress is good. Good estimation. No action needed to be taken.
89 Deployment to server 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
90 Test on deployed version and debug 2 3 0.67 High Delay due to bugs solving. Bug solving is assigned to a pair.
91 Deployment to server 1 1 1 Neutral Progress is good. Good estimation. No action needed to be taken.
Index for Iteration 6: 1(NEUTRAL IMPACT LEVEL)


An Overview

The Schedule Graph