[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [epf-dev] Discovered Size of OpenUP/Basic
- From: Mark.Dickson@xxxxxxxxx
- Date: Fri, 1 Dec 2006 10:13:54 +0000
- Delivered-to: email@example.com
- Importance: Normal
I think we should worry less about the number of pages and more about the value of the content on each page.
The number of pages will be artificially bloated by the page layout delivered by Composer. For example the Architecture work product covers two pages of printed paper but only delivers about half a page of text in a 12pt font.
On a more general point, I am uncomfortable about the way recent discussions have focused on the size of the process, as if somehow smaller means more agile. I do not believe that agility is a function of the size of the process. It is a function of how people behave, not what the process does or does not explicitly document.
I believe that it is important that OpenUP/Basic delivers value to it's users. I do not think that the primary audience for OpenUP/Basic is going to be projects made up of small teams of battle-hardened agile development veterans. Projects like that don't really need to refer to *any* written process.
So who's our audience? Small teams of less experienced developers adopting new technologies and techniques? People who want to use the Unified Process but want a free alternative to RUP? I think so. If that is the case then OpenUP/Basic had better be delivering some real content - by which I means actual practices and guidance to help them reach a point where they don't need it anymore.
That stuff consumes pages. And (if done right) delivers value.
When deciding what to chop out of OpenUP/Basic, we need to make sure that we ask the question "does this content deliver value to our audience?" If the answer is yes and we are still at 542 pages, then I am ok with that.
Principal Solution Architect
m 0780 1917480
-----epf-dev-bounces@xxxxxxxxxxx wrote: -----
To: "Eclipse Process Framework Project Developers List" <epf-dev@xxxxxxxxxxx>
From: "Scott W. Ambler" <swa@xxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx
Date: 12/01/2006 03:49AM
Subject: Re: [epf-dev] Discovered Size of OpenUP/Basic
Seems to me that we need to cut it down dramatically.
What material can we move out into separate plug-ins?
On Thu, November 30, 2006 7:56 pm, Jim Ruehlin said:
> The best estimate I have so far of the size of OpenUP/Basic is 542 pages
> (8 ½ x 11). This is based on what?s in CVS as of 11/29/06. This should
> give us an initial benchmark for our OpenUP/Basic 1.0 scoping efforts.
> I determined the size by creating a PDF of the entire website, doing a
> breadth-first walk along the links starting with the Intro page. I didn?
> t see anything missing, but I only made a cursory examination of the PDF
> file. Glossary terms, templates, and examples are included in the page
> count. Also, many web pages are longer than 8 ½ x 11, so this estimate
> is based on a book layout, not a website layout.
> - Jim
> Jim Ruehlin, IBM Rational
> RUP Content Developer
> Eclipse Process Framework (EPF) Committer www.eclipse.org/epf
> email: jruehlin@xxxxxxxxxx
> phone: 760.505.3232
> fax: 949.369.0720
> epf-dev mailing list
Practice Leader Agile Development, IBM Rational
Refactoring Databases (
http://www.ambysoft.com/books/refactoringDatabases.html) is now
epf-dev mailing list
Whilst this email has been checked for all known viruses, recipients should undertake their own virus checking as Xansa will not accept any liability whatsoever.
This email and any files transmitted with it are confidential and protected by client privilege. It is solely for the use of the intended recipient.
Please delete it and notify the sender if you have received it in
error. Unauthorised use is prohibited.
Any opinions expressed in this email are those of the individual and not
necessarily the organisation.
Xansa, Registered Office: 420 Thames Valley Park Drive,
Thames Valley Park, Reading, RG6 1PU, UK.
Registered in England No.1000954.
t +44 (0)8702 416181