Presentation about the Satama Unified Process (SUP) as it fits in the Satama organization. A bit about how the design documentation was created, what it looks like, how much time it took, and how it is linked to other processes in the company.

1. Satama Unified Process: Synergy on the work floor Presentation at SIGCHI.NL 2002 Summer Conference “Synergy Unlimited”, June 19, 2002 Peter Boersma ( peter. boersma @ satama .com ) Boyd de Groot ( boyd .de. groot @ satama .com )

3. What is SUP?

4. What is SUP? SUP is Satama’s delivery process A framework SUP helps in writing proposals and project plans Supports us: sell and do right things SUP is a collection of deliverables: templates and examples Increases efficiency and knowledge sharing SUP also contains instructions on parts of the delivery process Supports us to do things in the right way

5. Satama Unified Process ITERATIVE INCREMENTAL USER CENTRIC ARCHITECTURE CENTRIC 7 (+2) Workflows 5 Phases 4 Principles

6. Main Deliverables of SUP 1.0 Discovery Scan Inception Elaboration Construction Transition Analysis Insight Customer representation & Online offering Functional & Supplementary Requirements Interaction & Technical Design User & Technical Prototype Usability, Technical & eBrand Validation Launch Plan Project & Scope Plan Customer representation & Online offering Functional & Supplementary Requirements Interaction & Technical Design User & Technical Prototype Usability & Technical Validation Launch Plan Project Plan Interaction & Technical Design Software components Technical Validation Production environment Project Plan Guidelines Usability & Technical Validation Launched Service Project Plan & Closing Document VI Validation VII Launch Project management IV Analysis & design III Requirement capture II Business modeling I User exploration V Implementation

7. The SUP 1.0 Booklet

8. The SUP Deliverable Database

14. SUP is linked to other processes Satama Unified Process Resource management Billing Account management Competence development New business development Partner management Start a project Manage client relationship & expectations A framework to define competence needs Staffing A framework to manage sub-contractors Input for billing Evaluate the service and identify development opportunities

17. SUP Applied!

20. Design Program Framework II. Core process: III. Program support Design & Development Process: SUP Styleguide: Guidelines and Reusable Components Organization chart People / Competences Partner cooperation Administration/ Finance Information / Knowledge Technology / Tools I. Project Portfolio Content Mng / Maintenance Releases / Service line updates Explorative design Business Strategy Business plan Target Groups Technology Plan / Roadmap “ Lighthouse”: Vision Development

21. Project Portfolio and SUP Lighthouse (continuous project) / Horizon: 2-3 years / Accent on workflows: 1,2, hi-lvl 3 Explorative design / Horizon: 1-2 years / Accent on workflows 1,2,3, hi-lvl 4 (mock-up’s) Releases / Hor: 0.5-1 yr / Workflows: 3-6 CM + Maintenance / Horizon: present / Accent on workflows: 5-7 Workflows 1-7

24. Questions? Peter Boersma peter. boersma @ satama .com Boyd de Groot boyd .de. groot @ satama .com