• Save
Enterprise agile and how to succeed with it by Sergey Zabaluev
Upcoming SlideShare
Loading in...5
×
 

Enterprise agile and how to succeed with it by Sergey Zabaluev

on

  • 698 views

Presentation has been demonstrated by Sergey at Agile Riga Day 2011

Presentation has been demonstrated by Sergey at Agile Riga Day 2011

Statistics

Views

Total Views
698
Views on SlideShare
698
Embed Views
0

Actions

Likes
1
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Enterprise agile and how to succeed with it by Sergey Zabaluev Enterprise agile and how to succeed with it by Sergey Zabaluev Presentation Transcript

    • Enterprise Agile andHow to Succeed with itMarch 5, 2011Sergey Zabaluev,C.T.Co
    • IntroductionSpeaker: Sergey Zabaluev, C.T.CoExperience with Agile: Since 1999 implemented iterative and incremental delivery models in projects with distributed global teams Agile coach in multiple projects Managed large scale agile enterprise application development projects (e.g. with distributed teams of 70 people across Europe, US and Asia) Currently overseeing a portfolio of agile programs and projects Promoting agile methods among the enterprise customers Helping business and IT managers transition to Agile page 2
    • How We Got Startedwith Agile page 3
    • Large Enterprise IT – Environment and Challenges1 Complex IT landscape with thousands of applications2 Distributed teams, located across US, Europe and Asia3 Contracted, multi-sourced development4 Mix of agile and non-agile teams5 IT governance & EA standards and processes6 Yearly budgets set before the detailed project scope7 Tenders, fixed price contracts, conflicting goals of different stakeholders (e.g. business vs sourcing) page 4
    • Putting Agile into Context page 5
    • Applying Agile to Large Enterprise Environment +How to reconcile agile values with reality of large corporate IT? page 6
    • Agile Spectrum “Vanilla” Agile “Enterprise” Agile• Co-located small teams • Distributed large teams• Little or no discipline • Defined disciplines (PM, BA, IT Lead /specialization Dev Manager, Architect,• Customer on-site Developers, Testers, SCM Engineers)• Face-to-face • Multiple remote customerscommunication model • Hybrid communication model• Paper / whiteboard – • Collaboration tools-based coordinationbased coordination • Solution definition using lightweight• Solution definition using specification (use cases, datauser stories and dictionary, system rules, UI spec,acceptance criteria interface spec) page 7
    • Enterprise Agile Framework1 Agile Program Management2 Release Structure & Architecture-Centric Approach - RUP3 Project Management Practices – Scrum/XP4 Agile Requirements Practices – Collaborative Specifications Development5 Agile Testing 6 Development Practices Practices - XP7 Agile SCM Practices page 8
    • Release Lifecycle Phase 1 Phase 2 Phase 32 weeks – 2 months 2 weeks – 2 months According to project timeline Initiation Elaboration Construction Transition Operations 1-2 iterations 1-2 iterations 1..n iterations 1-2 iterations 1..n iterations Release Architecture Iterations Ready Production Production planning baselined, test delivered for rollout patch completed strategy defined UAT (if needed) (release Iteration Iterative dates, scope planning specs items, completed development Legend: iterations schedule) Enough specs to Incremental Bi-weekly initiate acceptance iteration page 9 development testing completion
    • Estimation Framework• Takes into account all keyproject disciplines, activities andbuffers• Accounts for estimate variationsbased on uncertainty• Includes the sizingmodel, estimation model andestimation process• Relative story point sizing used• Model accounts for release Scope Functionalityphases, as well as additional Initial Amended Scheduleactivities like reviews, non- Elaboration Construction Transitionfunctional aspects, defect fixing Effortand scope increase buffers, etc Staffing• Calculates efforts,schedule, staffing and costs Costs page 10
    • Iteration Planning WEEK 5 WEEK 6 WEEK 7 WEEK 8 WEEK 9 WEEK 10 WEEK 11 ITERATION RECEIVABLE PRE-ITERATION IMPLEMENTATION DELIVERABLE POST-ITERATION Specifications Development 1 review and processes Acceptance Stabilization clarification, review and processes Finalized functionality Testing Software adjustment specifications design processes package ITERATION RECEIVABLE PRE-ITERATION IMPLEMENTATION Specifications Development 2 review and processes clarification, Stabilization processes Finalized functionality Testing specifications design processes ITERATION RECEIVABLE PRE-ITERATION IMPLEME Specifications Development 3 review and processes clarification, Finalized functionality Testing specifications design processes• Overlapping iterations, with bi-weekly delivery cycles• Delivery is installed on the customer environment and goes through testing• Delivery is followed by the demonstration and acceptance by the customerrepresentatives• Release notes are provided with each delivery, outlining what scope itemswere included in the delivery and what are the outstanding defects page 11
    • SummaryYou can stay true to Agile valuesin large corporate enterprise ITenvironment keep the core principles adapt some practices introduce some new practicesAvoid binary and dogmaticthinking, be pragmaticResearch the methods, study theexperience, tailor it to yourcontext, experiment andsucceed! page 12