meta data for this page
  •  

This is an old revision of the document!


grp3 - Workload Forecast System

  1. Poorang Vosough
  2. Nikolaos Paraschou
  3. Negin Banaeianjahromi

Idea

After we received the requirement, we read it carefully and identified user stories. Then, we prioritized user stories into three levels based on their importance in our view of point and also based our time limitation. Later on, we discussed about list of works we were supposed to address during the next sprint so we identified product backlog. Finally we started our our one week sprint.

Scrum status

Product Backlog

  • User stories
Story ID Story name Status Size Spirint Priority
1 As a consultant, I need to be able to log into the system, so that I can use it based on my authorization. Done 4 1 1
2 As a consultant,I need to have a user friendly UI, so that I can interact with the system effectively. Done 2 1 1
3 As a consultant,I want to create a new project without approval. Done 3 1 2
4 As a consultant,I want to be able to enter my workload forecasts into the system so that managers and directors can use them. A workload forecasts can contain information like activity type, client, project/comment, prob-%, etc.). Done 10 1 1
5 As a consultant,I want to be able to save the forecast that I entered, in a database, so that it can be retrieved in future. Done 10 1 1
6 As a Manager, firstly I want to login to the system and be recognized as a manager. Done 4 1 1
7 As a Manager,I want to know exactly what are the workload forecasts of my team’s members and all data related to those forecasts (activity type, client, project/comment, prob-%, etc.). Done 10 1 2
8 As a Manager,I want to be able to read and edit the workload forecasts of all consultants. My purpose is to review the consultants’ forecasts and make corrections and additions to them. Ongoing 8 1 2
9 As a Manager,I want to see summaries and reports of workload forecasts. It is very important for me to know in real time what are the values of the following formulas: ARVE, URVE, COR. Ongoing 8 1 2
10 As a Manager,I want to see what is the availability percentage of each consultant per week. Ongoing 3 1 2
11 As a Manager,I want to see what is the activity forecast on a monthly basis (in percentage and in hours). Also, I want the estimated revenue (per activity per month) to be reported. Ongoing 5 1 2
12 As a Manager,I want to be able to edit (CRUD) users, user groups and teams. Ongoing 5 1 3
13 As a Manager,I want to add users and assign them to proper teams. Ongoing 5 1 2
14 As a Manager,I want the system to tell me “who did what and when”. For example, if consultant X updated his workload forecast for activity Y, I want to know about it. Ongoing 5 1 3
15 As a Manager,I want to print reports. Ongoing 2 1 2
16 As a Director, firstly I want to login to the system and be recognized as a director, so that I can browse forecasting data and the summaries of them. Done 4 1 1
17 As a Director,I want to see what is the activity forecast on a monthly basis (in percentage and in hours). Also, I want the estimated revenue (per activity per month) to be reported. Done 5 1 1
18 As a Director,I want to see the estimation of how much is left from total workload in percentage. Ongoing 3 1 2
19 As a Director,I want to be able to see the current forecast immediately after user changed data in database. Ongoing 5 1 2
20 As a Director,I want to be able to see ARVE (Assignment Rate Vacation Excluded), URVE (Utilization Rate Vacation Excluded) and COR (Charge-Out-Rate). Ongoing 5 1 2
21 As a Director,I want to see the modification history. Ongoing 5 1 1
22 As a Director,I want to print reports. Ongoing 2 1 2

Sprint Backlog

  • What we planed to do

coming soon…

  • What we managed to do

coming soon…

  • What we couldn't do/why?

coming soon…

Screenshots

Data base

Application

Coming soon….

Code

Upload and attach the .war package for final delivery

Upload and attach your project source code package here.

  • Clean up compiled binary files before making package
  • Use .zip format

Conclusion

What was delivered, how

coming soon…

Our experiences on code camp

  • Working as a team and trying to achieve a mutual goal.
  • Working in a very limited period of time with a strict deadline.
  • Competing with other teams and trying to be the best.
  • Being familiar with new concepts such as Agile software development and Scrum methodology.
  • Programming with a new tools such as Grails.

Final presentation slides

coming soon…