1	Agile RUP^® for a Pizza-sized Team Vladimir Savchenko BASS OT Inc. vladisa@bassot.com
2	From spaghetti code to pizza team Holy war of methods: RUP^® vs Agile RUP^®: plan-driven process What made RUP^® unified also made it appear as a “heavy-weight” Agile: lean & chaordic What made Agile a lean process also created ambiguity in interpretations Happy marriage is possible in a “Pizza-sized” team.
3	Our Success Story: Two projects 1^st COMPATTI^® E-comm services for the half-billion dollar on-line dating industry. Business evolved from market analysis & user feedback. Requirements with use-case driven approach, managed by non-IBM^® Rational^® tools. Team of 6, had 5 releases with 3-4 iterations per release.
4
5	Success Story #2 CBC CBC: web-based system for commodity trading firm with multiple offices. Business use cases identified for computerized automation Requirements managed with ReqPro Automated stakeholders’ feedback: RequisiteWeb Change management; ClearQuest/ClearCaseLT Team of 8 delivered the system in 7 months with 3 iterations.
6
7	Use case realizations – release versions
8	Activity Diagram - tool for storyboarding Use Case scenarios better described with Activity diagrams Text alone can’t handle logic well Each activity further elaborated with sequence diagrams Describe Use Cases as user’s manual!
9	Sequence diagram for storyboard scenarios
10	Team: Pizza-sized, 6-8 members A functional team could be fed with one pizza (6-8 slices) 7-9 team members is the most productive team (Grady Booch, RUC 2001) Amazon.com success with 5-7 people teams (Jeff Bezos) Big project? – divide & conquer with several Pizza-sized teams
11	Tools Requirements Management: ReqPro (alt: CaliberRM, Doors) Tasks management: ClearQuest, ProjectPlace.com Visual Modeling: Rose or Together Dev tools: J2EE (JBuilder, Eclipse) Testing: Test manager & ClearQuest Version Control: ClearCase or VCS
12	Process 1 Re-using components reduced development time Reverse engineering of code improved quality Adopted RUP^® as guidelines & scaled down to essentials Augmented with Agile techniques like… XP pair-programming Agile’s tacit knowledge exchange falls down in geographically remote team. Visual models with adequate documentation Architecture centric development requires longer initial iteration Use-case driven approach helps manage complexities
13	Process 2 PM: change your management style & productivity measurements Delegate some of your tasks to developers Wear many hats & share them with others
14
15
16