Software Project Management - Lesson 4 - Planning phase - Homework - Feedback

Sep 12, 2026

Homework assignment and feedback checklist for the Software Project Management Lesson 4 planning phase, focused on structuring a work breakdown structure (WBS) and defining execution details in a time schedule. The task set requires selecting a WBS structuring approach (function/object/process/mix), listing sub-projects/work packages, preparing a milestone plan with clear criteria and IDs, and documenting when work packages should be executed. Feedback specifies WBS ID coverage, minimum effort significance, milestone visualization, criterion specificity, and milestone date consistency against the course timeline.

LanguageEnglish

CategoryPresentations

FormatPDF

Pages7

Reading Time3 min

AccessFree to download

Homework

1. Download resources

2. Work breakdown structure (WBS)

3. Time schedule

4. Optional project management tools

5. Submission deadline and contact

Feedback

1. WBS feedback

2. Milestone plan feedback

3. Time schedule feedback

Software Project Management Lesson 4 – Planning phase Homework – Feedback Uwe Gühl Winter 2015 / 2016 Homework 1 . Download from [https://mike.cpe.ku.ac.th/](https://mike.cpe.ku.ac.th/) ~uwe/01219343 – Work breakdown structure template – Time schedule template – Milestone plan template Winter 2015 / 2016 Uwe Gühl -Software PM 04 Homework Feedback 2 Homework 2 . Work breakdown structure (WBS) a. Decide how to structure the WBS of you project (function, object, process, mix) b. List at least 7 Sub project / Work package items 3 . Time schedule a. Milestone plan Prepare the next milestone of your project. List at least three criteria to be checked b. Time schedule List at least 7 Sub project / Work package items and document, when they should be executed. Winter 2015 / 2016 Uwe Gühl -Software PM 04 Homework Feedback 3 Homework 4 . Alternatively you could use a project management tool like MS Project or ProjectLibre ( [www.](www.projectlibre.org)[projectlibre](www.projectlibre.org)[.org](www.projectlibre.org)) for tasks 2b. and 3b. 5 . Send the documents (office format or pdf) until 16.02.2016 to [uweguehl@hotmail.com](uweguehl@hotmail.com) Winter 2015 / 2016 Uwe Gühl -Software PM 04 Homework Feedback 4 Feedback 1 . WBS a. There should be an WBS ID for every work package (WP) . b. Consider only WP with at least 4 hours effort – effort of a WP should be significant higher (days / weeks) c. Sprint 1 Planning, Sprint 2 Progress report Proposal: WP Sprint Management d. Org chart: No assignments required Winter 2015 / 2016 Uwe Gühl -Software PM 04 Homework Feedback 5 Feedback 2 . Milestone plan a. Milestones listed should be visualized in time schedule b. Every criterion should have an id c. Criterion should be related to content, not in general Criteria to check: 􀀁 Submit first sprint report 􀀁 Update status by comment from Milestone1 􀀁 Advisor accept an update status Winter 2015 / 2016 Uwe Gühl -Software PM 04 Homework Feedback 6 Feedback 3 . Time Schedule a. Milestone(s) should be entered b. Proposal: Milestones at least every 4 weeks (compare to sprints) 􀀂 To check, if WP are done c. Dates of Milestones should fit Mismatch: located in CW15 (15.04.), with date 24.03.16 Winter 2015 / 2016 Uwe Gühl -Software PM 04 Homework Feedback 7

FAQs

What is required for the WBS in Homework 2?

Decide how to structure the WBS (function, object, process, or mix) and list at least 7 sub-projects/work package items.

What must be included in the milestone plan for Homework 3a?

Prepare the next milestone and list at least three criteria to be checked, with criteria that are content-related and identified with an ID.

What criteria are used in the feedback for the time schedule dates?

Milestones should be entered and milestones should align with sprint cadence (at least every 4 weeks), and milestone dates must fit the course timeline without mismatches.

Sep 12, 2026

Uploaded by Bill Black