Getting started with Agile can be confusing and it can also be difficult to move forward when you feel stuck. Learn how to understand the reasons for adopting Agile in the first place and how your Organization parameters (size, structure and culture) affect how you shape your adoption path.
1 of 25
More Related Content
How to Get Started with Agile when You Don't Know Where to Start
1. Agile FTW! How To Get Started With Agile When You Don’t Know Where to Start Before you get too settled in, we’re going to do an exercise so you might end up at a different table!
2. Create Your Learning Group Take a sheet of paper and write down: what do you want to learn today? what can you offer to other people here? Tape your sheet to your chest Mingle and create your learning group! Tip: if you’re here with a co-worker, try sitting in different groups to gain other perspectives
3. “ Everybody wants to be Agile, too few actually want to do it” - Ron Jeffries
9. Exercise In your learning groups: Brainstorm questions you want this session to answer (10 minutes) Cluster similar questions (5 minutes) Designate someone to put your stickies on the corresponding flip-chart Big company, rigid process How can we make Scrum work when people are working on multiple projects?
11. Understand Organization Size Bigger Organizations: more complexity processes are harder to change slower adoption pace complex politics difficult to cross boundaries “ Agile can’t work here” Syndrome
12. Understand Organization Structure Crossing Boundaries: difficult to create cross functional teams departmental incentives business vs development vs IT How to understand it? map it out on the wall note your sphere of influence separate response from resistance
13. Understand Organization Culture Choose Process wisely: control cultures like process and metrics collaborative cultures can use ‘blackbox’ processes cultivation cultures invest in people competence culture strive to be the best How to Understand Culture? Schneider Culture Model
14. Understand People are Different People are not linear: “ people go through changes at different rates and intensities” (Gerry Weinberg) How to Understand People? Myers Briggs (MBTI)
15. Example conflict! Challenges: ‘ scrum team’ forced to follow existing processes Dev vs QA vs IT vs PMO vs Business PMO called projects “agile” to bypass bureaucracy
22. Group Discussion How can you shape your adoption based on this model? How can you apply this model to your questions? Write down at least one activity you will commit to in order to get started
24. Group Discussion II Looking at what you wanted to learn here today, did you accomplish it? why? why not?
25. Thank You and Next Steps Jason Little @jasonlittle http://www.agilecoach.ca Online Peer Support Community: http://www.getagile.ca Download Materials htt p://www.agilecoach.ca What did you think? Please fill out a feedback sheet! Join me in the Coach’s Corner Area!
Editor's Notes
-ask how many are brand new to agile, how many have just started their adoption and kinda feel stuck - mqube story
- story2: q4, sentry updates
- bring focus to other sessions, disclaimer that agile isn’t magic and talk about why it isn’t, setup upcoming model slides
- tell the story from lisa/janet’s monday session (whole team doesn’t plan etc)