[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [epf-dev] Re-positioning and re-architecting OpenUP proposal
|
At 06:18 PM 7/31/2006, you wrote:
High-level Story
OpenUP consists of 3 sub-processes:
A sub-process for Management
A sub-process for Intent Management (name TBD)
A sub-process for Development.
I think that we need something for deployment too.
The sub-processes integrates nicely into a
cohesive process, but can be easily updated to
reflect different approaches to Management,
Intent Management, and Development. These 3
sub-processes rest on a layer of collaboration,
see Figure 1, to reflect the true collaborative
nature of OpenUP, and to make sure that the 3
sub-processes integrates into a cohesive whole.
<<Figure removed>
Each sub-process is packaged as a separate
plug-in, making it easy to swap out, for
example, one variant of Development to another
approach to Development. For the sub-processes
to be tightly integrated there needs to be some
glue. There are two central artifacts that exist
in each sub-process; A Vision and a Work Item
List. The Vision ensures that the work in each
sub-process is centered on a shared
understanding of what to produce, and Work Item
List is the intersection between requirements,
their implementation, and management of the
work. Also, Test Case, and potentially Test Data
is shared between Intent Mgmt and Development,
and Test Log is shared between Management and
Development. No tasks or guidelines are shared
between the sub-processes, but all roles are shared.
We also need source code, the system itself, and supporting docs I suspect.
Each of these sub-processes, as well as the
collaboration layer, is supported by a Principle
guiding the work for that sub-process, and each
Principle is also supported by a series of more
detailed Practices. Principles and Practices may
also be relevant for the other sub-processes. The mapping is as follows:
Management Evolve to continuously obtain feedback and improve.
Intent Management Balance competing priorities
to maximize stakeholder value.
Development Focus on articulating the architecture.
Collaboration Collaborate to align interests and share understanding.
Each of the sub-processes and the collaboration
layer also supports a statement in the Agile Manifesto:
Management Responding to change over following a plan
Intent Management Customer collaboration over contract negotiation
Development Working software over comprehensive documentation
Collaborate Individuals and interactions over process and tools
Still need to bring deployment into the picture.
- Scott
====================================================
Scott W. Ambler :-)
Practice Leader Agile Development, IBM Rational
www.ambysoft.com/scottAmbler.html
Every organization gets the process that it deserves.
Refactoring Databases: Evolutionary Database
Design (www.ambysoft.com/books/refactoringDatabases.html) is now available.
