T-76.4115/5115 Software Development Process Framework. Jari Vanhanen. T-76.4115 Software process framework Project management Requirements engineering Quality assurance Design & implementation Iterations. Contents. Course Arrangements. Tools MSDN AA
Have you already found other challenges?
Creating and improving the process (work practices, tools etc.) is part of project management/QA.
Check more materials from SoberIT’s SE courses.
It is recommended to split a course’s iteration into two sprints.
Iteration planning meeting
Deadline for the PP Iteration plan Mo 4.10. 13:00 by e-mail to customer, mentor and teacher
Tip! Combine the nextiterationplanningmeetingto the iteration demo.
planning is more important than documenting its results, but documenting is also needed in this kind of a project
2. Stakeholders and staffing
5. Work practices and tools
7. Risk log
You can rotate or change the assigned roles within the group.
Define personal learning goals separately!
Increasing visibility to mentor
using low overhead approaches:
Report all project related hours such as studying etc...
including QA plan and description of work practices
progress reports (a slide set for the iteration demos)
Course provides some document templates
their use is mandatory, but irrelevant topics can be omitted
use a change log
clear and compact form
once and only once
give IDs to items (reqs, tests, …)
use spelling checker
send URL to 1)customer, 2)mentor, 3)teacher
www-page must contain separate documents and a zip-package
DL is 1-2 days before iteration demoDocumenting
get to know each other
find out about each other’s commitments and personal interests
discuss roles and responsibilities
good team spirit is crucial
Arrange a weekly, co-located work session
at least for sub teams
Start work immediately in the beginning of iterations
more calendar time to react to unexpected situations
Test unfamiliar technologies and tools early to minimize risks
Spy on others to get ideas
projects from previous years/this year
give a reference, if you copy some materialsProject Management - Hints
Find out using any possible means:
Re-estimate the “most important” requirements.
Choose iteration’s requirements.
Find out the details of iteration’s requirements.
Change management, status tracking, tracing
Review iteration’s requirements.
Get customer’s approval.
In practice many activities are parallel and iterative!
Re-estimate required effort.
Ensure realism of the plan.
Implementation, QA, Delivery
Collect feedback from the customer.
green = good
yellow = moderate
red = bad
white = don’t know
*** = large effect
** = moderate effect
* = small effect
<empty> = no effect
2 = good
1 = moderate
0 = bad
<empty> = don’t know
2 = high
0 = low
Consider also other relevant quality metrics such as defect counts, code metrics...