• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Agile and Traditional Management

Agile and Traditional Management



Agile and Traditional Management

Agile and Traditional Management
- key differences
- where we can use agile and why



Total Views
Views on SlideShare
Embed Views



1 Embed 2

http://baridoo.com 2



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.

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

    Agile and Traditional Management Agile and Traditional Management Presentation Transcript

    • Agile Methods Zuzi Sochova sochova.com @zuzuzka Introduction Session Agile and Traditional Management
    • What means Agile to you?
    • What means Agile to you? Agile is common sense so don’t be disappointed
    • What means Agile to you? Agile is philosophy based on people, collaboration and shared values Scrum, Kanban, XP,… are Processes
    • Different Agile Projects
    • Different Agile Projects Using agile principles I’ve been:Organizing and coaching many SW teams but as well Leading department of 100 people Implementing HR strategyCoaching the company business strategy Managing small startup company
    • Where Agile started?
    • Successful IT projects The agile process is the universal remedy for software development project failure. Software applications developed through the agile process have three times the success rate of the traditionalwaterfall method and a much lower percentage of time and cost overruns. according to the 2011 CHAOS Manifesto from the Standish Group.
    • Agile vs. Traditional Management
    • Agile ManifestoWe are uncovering better ways of developingsoftware by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
    • Why is Agile different? Agile is about trust in people while Classical PM is often about how to control people
    • Why is Agile different? Agile is good for complex and empirical environments
    • Why is Agile different? Software development is not a predictable process. Building another house often is. The predictable process needs a plan and control to stick to the plan and maybe adjust it a little bit when needed. Empirical process needs good change management and creativity.
    • Agile Adoption
    • Agile is Change Management http://quotesbank.org
    • Fundamental Difference about the View on People and Teams http://photos3.flickr.com
    • Learning and continuous feedback http://www.questcorp.com
    • Experience your own way http://www.zdn.cz
    • Cooperation
    • Responsibilityhttp://larryhehn.com
    • Global priorities http://theemptiness.info
    • Common Story http://abc.blesk.cz
    • On-time, Fast, Flexible, Predictable
    • Agile and Lean Processes used as process to any development
    • Agile and Lean Processes Agile team follows an iterative process that is lightweight, highly collaborative, self organizing, and quality focused.
    • Agile and Lean Processes A lean process continuously strives to optimize value to the endcustomer, while minimizing waste that may be measured in terms of time, quality, and cost. 
    • Scrum Process - Basics
    • Work in Iterations
    • Team Collaboration
    • Communication and Self-organization
    • Scrum Process – Summary
    • Agile and PMBOK PMBOK describes what should be done during the management of a project. Agile methodologies describe how to do the things that should be done. The approaches defined in the PMBOK® Guide—Fourth Edition and in agile are compatible. Agile can be used together with the PMBOK® Guide http://www.pmi.org
    • Agile and PMI – Scrum example Initialization • Same Planning • Scrum–like process, iterative functionality planning, adjust scope according to the customer feedback • how we communicate, organize team, roles Execution • Every iteration customer demo Monitoring • Retrospective, Sprint review Closing • Same • Acceptance every iteration
    • SummaryAgile principles are generally used to any complex empirical projects: Incorporate change (process, product) Implement Short Iterations Endorse self-organization  High collaboration Transparent Communication Continuous Learning Quality Driven
    • SummaryAgile processes are used inside project management
    • Zuzana Šochová, zuzi@sochova.comAGILE & SCRUM TRAINER, CONSULTANT AND COACHPersonal web: http://sochova.comEnglish blog: http://tulming.com Czech blog: http://soch.cz/blogTravel blog: http://asmat.euTwitter: @zuzuzka