Project work 18.03. - 10.04.
First rule of this project is - when something is not clear, ask. To ask the questions you can either choose to add ivom2gi in Skype or write to firstname.lastname@example.org. You will get the answers.
N!B! Questions for the interviews should also be sent to email@example.com.
At minimum we expect you to create the following deliverables by 10.04.2013 14:00 the latest:
- Description of the current status
- Current development and delivery process
- Roles and responsibilities within the team
- Problems with the current process
- Reasoning why these problems are relevant by estimating the impact
- Process improvement plan
- Inspired by the problems identified, goals for the improvement are set
- Proposals for process improvement are created and prioritised
- Explanation why those improvements are beneficial is present
- New process is defined based on the improvements is proposed
- Roll-out plan
- Plan how to roll out those changes in the process
- Measurement of the change impact is explained
- Criteria's whether the change was successful are created
- Results are presented in either 8.04 or 10.04. presentation sessions.
- 18.03 - introducing the project
- 20-22.03. - interviews with stakeholders
- 27.03. - tentative: if we find we need to hand out additional information there will be a lecture
- 28.03. - consultation sessions
- 08.04. - presentations for first group
- 10.04. - presentations for second group
- Narrative - online version of the document handed out in the lecture
- Additional notes from the interviews - NEW
- Issue Tracker - access using your ÕIS email as username and password given in the lecture
- Sample artifacts
- Status quo: 9pt
- Most important: The described process is reflecting the reality
- The current process is described in depths. You explain in details:
- when and how tasks move from one stage to another
- when people in certain role start working on a task
- when the task is considered to be ready for the next stage
- how the project planning takes place
- what happens when there are changes in the plan
- how requirements are gathered
- how the verification and validation take place
- Description of the current process is backed by the facts from data sources used (JIRA, sample documents, interview protocols, narrative, …)
- The format you use to describe the current process is for you to choose. We recommend to base the process description in a visual representation, such as a statechart diagram, annotate this to the extent you feel appropriate and give the rest of the details in textual format.
- Current roles and responsibilities are explained.
- At least five problems have been identified within the process. Problems discovered are backed by (likely) causes. Problems discovered are linked to the impact(s) the problem has to the development process. Pseudo-sample:
- Problem: Iteration deliverables contain too many bugs
- Cause 1: Developers are drinking too much coffee and their hands start to shake. So they end up typing in the wrong characters.
- Cause 2: ISV tester is color blind and short-sighted and does not discover the visual defects during the validation phase.
- Impact 1: $5,000 fine for each but discovered is charged from the ISV.
- Impact 2: LGO tester is forced to throw in 40 hours of overtime each month and has thus said he is going to leave the company in 2 months.
- The problems identified are backed with facts from the process described
- Impact of the problems is clearly explained.
- Improvement plan: 5pt
- Based on the discovered problems you have set measurable goals for reducing the impact of those problems. You explain why you are going to reduce the impact of those problems.
- You have picked the set of causes for those problems to be addressed. You explain why you have picked those causes and left out the others.
- You describe the new process based on problem causes you are proposing to address.
- Roll-out plan: 5pt
- You describe in which order you are rolling out the proposed changes.
- You describe who in the team is about to do what and when in order for the changes to be effective
- You describe when the impact of the changes will be measured
- You describe how the impact of the changes will be measured
- You describe how to decide whether a particular change was considered a success
- You estimate the total investment (time-wise or cash-wise) required to roll out the changes you propose. **You explain the possible impacts of those changes to the project deadlines.
- Process: 6pt
- Interviews: 2pt
- You have prepared for the meeting.
- You have at least 30 questions sent in advance (in total, not 30 to LGO and 30 to ISV).
- You take the lead in the meetings.
- You record the meeting notes.
- Final presentation: 4pt
- We understand the process you discovered to be in place
- We understand the problems you have discovered in the current process
- We understand the improvements you are proposing
- We understand the roll-out plan.
- We understand how you are planning to measure the outcome
- We find your presentation engaging
- You stay within time limits - 20 minutes per team
- Interviews: 2pt
Teams and meeting slots
|Rühm||Interview with ISV (Ivo)||Interview with LGO (Artur)||Consulting||Presentation|
|Groupimg||Wed 10:00 @ L2-225||Thu 12:00 @ L2-225||28.03. 10:15 @ L2-225||10.04. 14:15 @ L2-403|
|Kolm||Wed 17:00 @ L2-225||Thu 17:00 @ L2-225||28.03. 17:00 @ L2-225||08.04. 12:15 @ L2-403|
|Hotrats||Wed 14:00 @ L2-225||Thu 13:00 @ L2-225||28.03. 13:00 @ L2-225||08.04. 12:15 @ L2-403|
|P126||Wed 16:00 @ L2-225||Thu 11:00 @ L2-225||02.04. 12:00 @ L2-315||08.04. 12:15 @ L2-403|
|Bad Money||Wed 15:00 @ L2-225||Thu 14:00 @ L2-225||28.03. 14:00 @ L2-225||10.04. 14:15 @ L2-403|
|Kas Peab Nime Valima||Wed 13:00 @ L2-225||Thu 15:00 @ L2-225||28.03. 12:00 @ L2-225||10.04. 14:15 @ L2-403|
|Nokia||Fri 13:00 @ L2-315||Fri 17:00 @ Nortal||25.03. 14:15 @ L2-315||08.04. 12:15 @ L2-403|
|Random||Fri 12:00 @ L2-315||Fri 16:00 @ Nortal||28.03. 15:00 @ L2-225||10.04. 14:15 @ L2-403|
|Mihkel||-||-||28.03. 11:00 @ L2-225||10.04. 14:15 @ L2-403|