Last modified 16 years ago
Last modified on 10/29/08 17:22:40
Analysis
Overview
The exported results from our work breakdown structure are used for better tracking of our work process and early discovering of potential impediments. We track our workflow with daily reports, they are written according to a specific template. This way we can extract from them desired information using a script. For this revision of the task your goal is to create a script that checks the reports and ouptuts useful statistics.
Task requirements
Create script that:
- checks if the reports are correct
- if they are not correct displays the number of errors
- outputs useful information related to the work breakdown structure
- working hours on task
- total working hours
- on how many tasks anyone has worked
- etc.
Task result
The result of this task must be script file that should be stored in the repository.
Implementation idea
Create a python script that fulfill the task requirements.
Related
SCHEDULE_WBS_EXPORTS_R0 SCHEDULE_MAINTENANCE_R1
How to demo
Run the script and check your daily reports.
Design
- create a file named statistics.py
- contains statistics computed from daily reports.
- should be put in one of the directories m0*, where * = 1...12 , in order to see the results.
- Contains the following things:
- Time spent (in hours) working.
- All the tasks a person has worked on throughout the sprint. These include an, an-re, de, de-re etc... This section is a union of the following subsections:
- Implemented tasks - the tasks that are NOT re
- Reviewed tasks - the tasks that are re
- Note: 'an-re SCS_INFORMATION_R0' goes in reviewed tasks while 'im SCS_INFORMATION_R0' goes in implemented tasks.
- Reviews and implementations - this is the intersection of the prior subsections. This indicates whether a person has spent time on doing both reviews and implementations of a phases of a task.
- Untracked things - these include tasks that do not have corresponding issues in the issue tracker.
- Comments - this sections includes things that have to be improved. For the time being we have:
- Untracked activities - we should avoid doing things that are untracked. In general this means we are not going towards the goal. DO NOT PAY ATTENTION TO THINGS LIKE UNTRACKED_SPRINT_OPEN since this is a plausible untracked activity.
- Things that are done over and over again like an2, de2, im2. This means that a task is not done accurately of the fly. Phases like an-re2 that have re part are not included since the person reviewing is not guilty for not passing things that are not done correctly.
Implementation
- done according to design => Statistics
Testing
Comments
Log
