Methods Over Madness 2003 Ver

Chicago Rational User’s Group – October 14, 2009

What defines a good methodology?

Are you a Mad Hatter? OPENUP Peek 5 important things

about Rational Method Composer

RMC / OPENUP Demo Q and A

04/10/23 The Nimblestar Group, Incorporated copyright - 2009 all rights reserved

2

Criteria Compliance assures a higher percentage of

successful projects Compliance adds value to the project Flexible and dynamic to your project’s needs One current content source available to all Activities performed subscribe to Agile principles Organized and published by practitioners /

methodologists All staff using it trained on its use Enforced controls in place to assure compliance

IT Process Audits for projects in place Gates or checkpoints for progress enforced


3

Project Management often feel like you are presiding over the tea party? Projects late? Over budget? Not delivering what’s

expected? Wondering how to

grab control?


4

How many projects are: “New” development?

Stick built / developed vs. COTS? Trend is toward more COTS with “glue” apps to

existing systems Enhancement Maintenance?

Ver. 2.1, 2.2, 2.3 of a system in place Repair Maintenance?

Hands full of fixes compiled into a release? For one or more subsystems in one or more

applications?

Versus KTLO (Keep the lights on) Support04/10/23 The Nimblestar Group, Incorporated copyright - 2009 all rights

reserved5


6

%

5% to 15 % NEW Development

10% to 30% Enhancement Maintenance

20% to 35% Repair Maintenance

65% To 20% KTLO (Keep the lights on) Support


7

NEW

Enhancement

Repair

KTLO Requir

em

en

ts c

om

ple

xit

y

Vision, Use Case Model,Use Cases, Declarative Requirements StoryBoard,Data Model etc…

Issues, Updated Use Cases, Declarative Reqs, Glossary

Issues, Declarative Reqmts.Maybe Use Case updates

Issues

Offshore development Lack of specifications from COTS packages Time / dollar burn rate / complexity goes

up from bottom to top of project pyramid Technology complexity Business change and complexity Lack of knowledge on part of business and IT


8

“You cannot control what you cannot measure” - Tom DeMarco (circa 1983)

IBM proposes “Measured Capability Improvement Framework - MCIF” drive business innovation

through measured and continuous process improvement


12

“No wonder you're late. Why, this watch is exactly two days slow” – The Mad Hatter…

To improve software delivery capability - teams must scale agile practices deliver more for less correlate business outcomes with investments in processes

and tools produce higher quality in faster delivery times.

MCIF can help you: Adopt an incremental, measured approach to transformation Focus on the core practices that matter most Accelerate adoption through ready to use assets Articulate capability improvements in terms of business value Support any method, particularly optimization for agile

practices


13

Project Related: Critical Situations Defect count / severity Defect latency Overall project health Velocity Burn Rate

Application Related: ROI – Development cost TCO – Development and support cost


14

For disciplines Use Delphi techniques for estimating effort Practical and Pragmatic exit criteria

For projects - Elapsed time Can I finish this project under a year?

If no – throw something out – change the game Time related:

Measure ½ of elapsed time Using MCIF Measures - Ask: “Am I half done?”

If no – start damage control


15

Project Management PMO, Program Management, Executive

Management Governance

Silo’ed organizations – Ops, QA, Security, Audit Manufacturing

Requirements, Analyze / Design / Develop / Test / Refactor

Delivery Change management Configuration management Deployment


16

Almost all shops focus on these 4 areas Each IT Shop different Focused around their mission Governance least addressed – most

effort The more silos the worse it is for a project Silos cause a lot of added effort to basic

methods


17

How many of these can you address with methods? 1. Business productivity and cost reduction 2. IT/Business alignment 3. Agility and speed to market 4. Business process re-engineering 5. IT cost reduction 6. IT reliability and efficiency 7. IT strategic planning 8. Revenue-generating IT innovations 9. Security and privacy 10. CIO leadership role

Source: CIO Insight results from 2009 annual survey of top ten priorities of CIOs


18

Good Enough is Good Enough These are Best Practices, meant to be

customized to your project And the Patterns are meant to be customized

Too often teams fail with “out of the box” practices Pay attention to all four areas of concentration

Too often only Manufacturing and PM are addressed There are some “Musts” for artifacts

And they ought to be indicated for the team Governance may demand certain artifacts for

certain projects Regulation or law may require artifacts


20

What is OpenUP? OpenUP is a lean Unified Process that

applies iterative and incremental approaches within a structured lifecycle.

OpenUP embraces a pragmatic, agile philosophy that focuses on the collaborative nature of software development.

It is a tools-agnostic, low-ceremony process that can be extended to address a broad variety of project types.


21

Counts

Business Classic OPENUP

Modeling RUP

Roles 6 31 7

Artifacts 31 105 24

Role and Artifact Counts

Simplicity to build on Iterative format Agile perspective Low Ceremony Focus on

Manufacturing

04/10/23 The Nimblestar Group, Incorporated copyright - 2009 all rights reserved 22

FYI, these are out of the box counts,And these processes as we said are meantto be customized to YOUR needs…

Classic RUP OPENUPProject Management 20% 5%

Governance 15% 5%

Manufacturing 45% 85%

Delivery 20% 5%

There are Tradeoffs These are

estimates of coverage

There’s room for growth

Flexibility for change

Customization key to adoption


23

For OPENUP, 5% estimates for Governance and Delivery are generous

Rational Method Composer or Eclipse Project Foundation - EPF

SPEM Model Content and Process

SPEM (Software Process Engineering Model)

• Quick Data Entry– Artifacts– Roles– Tasks– Plus other widgets

• Guidance• Checklists• Whitepapers• And more…

• WYSIWYG displays of content• Caution – Working with

provided content does require a familiarity with plug-in content

Capability Patterns Reusable chunks of process Used to assemble Delivery Processes

Order of work to produce

tables

Design chair Cut wood

Design table

Build chair back

Build table top

Finish table

Make legs

Install legs

Finish chair

Order of work to produce

chairs

• Picture driven navigation– Activity Diagrams drill down to tasks– Detail Activity diagrams drill down to roles, tasks,

artifacts • Context for shop content

– We are context owners for presentation– By utilizing links to existing shop oriented content,

Content owners can easily update their own content• Static Website

– Capable to link out to any type of app– Using EPF instead of RMC adds WIKI capabilities to

allow appending to content

All WBS are exportable to Microsoft Office Project Server (MOPS)

WBS matches exactly what is in the Methodology Website

Important information carried over Brief descriptions of tasks as notes Roles as resources Predecessors from Website Content WBS

Using Requirements Management and OPENUP


30

Rational Method Composer http://www-01.ibm.com/software/awdtools/

rmc/ Method Authoring Method – available

download http://www.ibm.com/developerworks/

rational/downloads/08/rmc_mam/ IBM / Rational Process library (Plug-in List)

http://www-01.ibm.com/software/awdtools/rmc/library/


31

IBM’s Measured Capability Improvement Framework (MCIF) http://www-01.ibm.com/software/rational/mcif/

OPENUP http://en.wikipedia.org/wiki/OpenUP http://www.eclipse.org/epf/

Eclipse Process Framework (EPF) http://www.eclipse.org/epf/

OMG-SPEM Model http://www.omg.org/technology/documents/

formal/spem.htm


32

Tom Weinberger The Nimblestar Group, Incorporated [email protected] 312-805-0470 www.nimblestar.com

Come join me on Linkedin at: http://www.linkedin.com/in/tomweinberger


33

Documents

Methods Over Madness 2003 Ver