ibm rational unified process by illia kochyzhev. objectives counterpose agile defend plan-driven...
TRANSCRIPT
IBM RATIONAL UNIFIED PROCESSby Illia Kochyzhev
OBJECTIVES
Counterpose Agile Defend plan-driven methods IBM RUP overview
ABOUT ME
20 years in Project Management IBM, Microsoft, Google Managing partner @ MC Ventures
7 years in Project Management SoftServe, PFSoft, Technopark Managing partner @ MC Ventures RUP, SCRUM, Kanban, Waterfall
AGENDA
Process Overview Time Dimensions
Phases Iterations
Static Structure Q&A
WHAT IS RUP
1. Software Engineering Process
2. Web-enabled, searchable knowledge
base
3. Guidelines, Templates and Tool
mentors
4. Tools?
BEST PRACTICES
1. Develop software iteratively
2. Manage requirements
3. Use component-based architectures
4. Visually model software
5. Verify software quality
6. Control changes to software
Requirements Analysis
Design
Code & Unit testing
Subsystem testing
System testing
TIME DIMENSIONS
Transition• Beta testing• Transition from legacy system• Conversion of databases• Trainings• Marketing and Sales
Milestone : Product Release
Inception• Vision• Use-Case model (10-20%)• Glossary• Business case and success
criteria• Financial forecast• Initial risk assessment. • Project plan• Prototypes.
Milestone : Lifecycle Objectives
Elaboration• Use-Case model (>80%)• Supplementary requirements• Software Architectural
Document• Executable architectural
prototype• Revised risk list and business
case• Development plan for whole
project
Milestone : Lifecycle Architecture
Construction• Integrated product• User manuals• Description of the release
Milestone : Initial Operational Capability
ITERATIONS
ITERATION OBJECTIVE
ArchitectureM 1
F1
UI1 UI2
F2
UI3 UI4
M 2F3
UI5 UI6
F4
UI7
Architecture
M 1
F1UI1
UI2
F2UI3
UI4
M 2
F3UI5
UI6
F4UI7
E1, E2
C1
C2
C3 C4 C5
RUP
ArchitectureM 1
F1
UI1 UI2
F2
UI3 UI4
M 2F3
UI5 UI6
F4
UI7
S1
S2
S3
S4
S5
S6
S7
SCRUM
STATIC STRUCTURE
Worker (who) Activity (how) Artifact (what) Workflow (when)
STATIC STRUCTURE
RUP vs SCRUM
IBM RUP SCRUMPlan No Plan
Little rework Lots of rework
Complex process Simple process
Lots of roles 3 roles
Lots of artifacts Few artifacts
Iterations Iterations
Multi functional team Cross functional team
Allows moderate changes Fits for changing environment
