©2008 Armstrong International, Inc. Basic Steam Trap Operation.
Armstrong Process Group, Inc. Copyright © 1998-2006, Armstrong Process Group, Inc., and others All...
-
Upload
elizabeth-clayton -
Category
Documents
-
view
229 -
download
3
Transcript of Armstrong Process Group, Inc. Copyright © 1998-2006, Armstrong Process Group, Inc., and others All...
Armstrong Process Group, Inc.www.aprocessgroup.com
Copyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
Armstrong Process Group, Inc.www.aprocessgroup.com
Copyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
Project Management Review
Eclipse Process Framework19 Jun 2006
2
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
ObjectivesReview OpenUP/Basic PM elements and EPF examples
Project planIteration planWork items listRisk listStatus assessment
Compare/align with ScrumRelease burndownProduct backlogSprint backlogSprint burndown
Discussing piloting (i.e. “testing”) OpenUP/Basic content
3
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
OpenUP Project Plan – DefinitionBrief description
This artifact gathers all information required to manage the project. Its main part consists of a coarse-grained plan, containing project phases and milestones.
PurposeThe purpose of the Project Plan is to provide a central
document where the any project team member can find the information on how the project will be managed.
4
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
OpenUP Project Plan – Implied Content Project constraintsScope and durationMeasurementsPhases and milestonesNumber, length, and objectives of iterationsStaffingDevelopment process
Implied content based on steps of Task: Plan the Project
5
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
OpenUP Project Plan – ObservationsImplied content does not match current template
Updating template already in BugzillaReally do not have an OpenUP Project Plan for EPF
projectDevelopment plan is closeDoesn’t appear to have been maintained
Didn’t we add another iteration?Iteration goals don’t quite line up any more; some should be
removed (i.e. agile stuff)
6
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
OpenUP Project Plan – ObservationsPut iteration “goals” in project plan
Similar to what is in current development plan for each milestone
Put iteration “objectives” in iteration plansBased on premise that goals are more abstract and coarse-
grained than objectivesShould OpenUP have a “release planning” element?
Should we rename the step in Task: Plan the Project “Plan project scope and duration” to “Plan releases”?
7
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
OpenUP Iteration Plan – Definition Brief description
This artifact is a fine-grained plan describing the objectives of a given iteration and how they will be evaluated. It contains a list of work assignments for the particular iteration.
PurposeFacilitating the communication of the goals, objectives, tasks
and assignment for a given iteration.
8
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
OpenUP Iteration Plan – Implied ContentObjectives (“high-level tasks” or “goals”)
Related to risks, timebox, requirementsIteration tasks (“smaller tasks”)Allocated work itemsElements to test
Implied content based on steps of Task: Initiate Iteration and Task: Plan Iteration
9
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
OpenUP Iteration Plan – ObservationsImplied content does not match current template
Mixes “objective” and “task” as same thingUpdating template already in Bugzilla
How to the “items” in the iteration plan relate to EPF metamodel elements?Are they activities, tasks, steps, descriptors, etc???
There appear to not be any iteration plans for EPF project
10
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
OpenUP Work Items List – DefinitionBrief description
This artifact contains all work that has to be done in project.
PurposeTo collect all work that has to be done in a project, so work
can be prioritized and effort estimated.
11
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
OpenUP Work Items List – Implied ContentNameTypePriorityEstimateRelease
Implied content based on Artifact: Work Items List
12
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
OpenUP Work Items List – ObservationsAppears that this is a collection of requirements and
change requests and tasksHowever, it is not the requirements or the change requestsIt is a convenient place to prioritize them
Used to assign work to individual team members for specific iterations
Perhaps work items are assignable tasks related to requirements and change requestsWhat do we do with tasks that aren’t related to requirements
or change request (such as process-related tasks like project planning and establishing a development environment)?
Should we just call this the “task list”?
13
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
OpenUP Work Items List – ObservationsAppears that Bugzilla is the work item list for EPF projectHowever, some “items” need to be broken down into more fine-
grained “item”For example, “#146662: All disciplines: no discipline text” might need to
be broken into smaller items, one for each disciplinePerhaps “All disciplines will have explanatory text” is the detailed
“requirement” and the items for each discipline are the “work items”There are no detailed requirements for EPF project documented
anywhereThere are change requests (and a lot of them for “missing”
requirements)
14
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
Scrum Product Backlog – Definition The Product Backlog is the master list of all functionality desired
in the productProduct Owner prioritizes the items in the Product Backlog Team determines which items they can complete during the
coming SprintThe team then moves items from the Product Backlog to the
Sprint BacklogIn doing they expand each Product Backlog item into one or
more Sprint Backlog tasks so they can more effectively share work during the Sprint
A very interesting prospect is expressing Scrum backlog items in the form of Extreme Programming's User Stories.
From Mike Cohn @ Mountain Goat Software
15
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
Scrum Product Backlog – ContentPriorityItem #DescriptionEstimateAssigned To
16
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
Scrum Product Backlog – ObservationsAs it is defined as a list of all product capabilities, it seems as
these are the product requirementsOpenUP Features, Use-Case Model, and Supporting Requirements
(and/or perhaps scenarios) are same as Scrum Product BacklogItems on product backlog are decomposed into smaller tasks on
sprint backlogImplies product backlog items and sprint backlog items are not the same
thing, but relatedIn certain situation a single product backlog item may become a single
sprint backlog items, but this may be the exception, not the ruleSupports idea than an OpenUP work item is one or many tasks related
to implementing a requirement or change request
17
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
Scrum Sprint Planning and AssessmentCollectively the Scrum Team and the Product Owner define a
"Sprint Goal," which is a short description of what the sprint will attempt to achieveThe success of the sprint will later be assessed during the Sprint
Review Meeting against the Sprint Goal, rather than against each specific item selected from the Product Backlog
During the Sprint Review Meeting the project is assessed against the Sprint Goal determined during the Sprint Planning MeetingIdeally the team has completed each task planned for the sprint but it is
more important that they achieve the overall goal of the sprint
Implies a distinction between iteration goals/objectives and tasks
18
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
Scrum Sprint Backlog – DefinitionThe Sprint Backlog is the list of tasks that the Scrum
Team is committing that they will complete in the current Sprint
Items on the Sprint Backlog are drawn from the Product Backlog by the team based on the priorities set by the Product Owner and the team's perception of the time it will take to complete the various features
19
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
Scrum Sprint Backlog – Content Assigned ToDescriptionEstimated effort per week
20
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
Scrum Sprint Backlog – Observations Appears to not be prioritized
Only the Product Backlog is prioritizedSprint tasks inherent the priority from their related backlog
items?
21
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
Scrum BurndownBurndown is a trend report showing the amount of work
remaining for a period of timeRelease burndown
Shows amount of work remaining based on “points” – measure of requirements coverage based on scope and complexity
Sprint burndownShows amount of work remaining based on time estimates
of allocated tasks
22
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
Relationships
Feature
Use Case SupportingRequirement
Related to Composed of Traceability
Work Item List
Work Item /Assigned Task
Change Request
Requirement
IterationTest Case
{xor}
0..1
0..1
comprised of
0..*
Team Member
0..*
0..*
1
1
Objective Risk
0..*
Product Backlog comprised of
0..*Process
Task
0..*
{xor}
0..1
23
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
Overall ObservationsRequirements are the product backlog
For OpenUP most of the “functional” detailed requirements are the process elements
Work items are the tasks for an iteration (sprint backlog)Based on requirements, change requests, and process
tasksStill need a separate iteration plan for objectives, risks,
and test casesProject plan contains iteration goals, but not detailed
iteration objectivesConsider adding releases to project plan
24
EPF Project Management ReviewCopyright © 1998-2006, Armstrong Process Group, Inc., and others All rights reserved
Piloting OpenUP/Basic ContentShould pilot subset of OpenUP/Basic on EPF project
Project managementRequirementsTesting
Identify external, commercial pilot opportunities