Agile Roles in a Flat Organization

Slides:



Advertisements
Similar presentations
Purposeful Senior Leader and Team Member Rounding Overview
Advertisements

The Leaders Guide to Radical Management by Stephen Denning Amazon Reviews: Startling clarity, common sense, and immediate relevance Management Innovation.
© Quality Solutions for Healthcare Team Leadership Programme Betsi Cadwaladr University Health Board Workshop evaluation from 25 th January 2012 Debbie.
Vodafone People Strategy (VPS)
Delivering Enterprise Projects Using Agile Methods Brent Barton May 23, 2006.
2013 CollaboRATE Survey Results
Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.
Archana Mehta. Spot a Failing project Costs a lot more than it should Its takes longer than anyone expected The product doesn’t do what it was supposed.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Maintaining Industrial Harmony at Work
CIPD Profession Map Sarah Koppen Profession Map Project Executive
Agile Teaming Concepts for and from the Facebook Generation Neil Rodgers NASA Enterprise Applications Competency Center (NEACC) 1.
Agile development By Sam Chamberlain. First a bit of history..
Introduction to Agile.
Agile Methodologies for Project Management By – Komal Mehta.
PAS: Scaling Agile – A real life experience November 4, 2009.
AgileCamp Presents: Scrum. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution 4.0.
Larry Apke Agile Expert
Dr. Tom WayCSC Software Processes CSC 4700 Software Engineering.
Disturbance Strategy to Achieve Self Organization.
AgileCamp Presents: Agile 101. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution.
SE503 Advanced Project Management Dr. Ahmed Sameh, Ph.D. Professor, CS & IS Agile Principles: Leadership-Collaboration.
Sri Lanka Institute of Information Technology Software Engineering Project – I Clone of Rally GROUP NO : WD-SEP-002 | PROJECT NO :25 PROJECT : CLONE OF.
4/23/ :45 PM © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered.
1 FROM DEVELOPERS TO ENGINEERS ENGINEERING ROLE IMPLEMETED AT EXPEDIA August 26, 2015.
MAKING BUSINESS AGILE Andrew Kallman, MBA, PMP, CSP 21 March 2013 NYC Scrum Users Group AGILE PROGRAM MANAGEMENT USING THE UNIFIED VISION FRAMEWORK.
Take No Prisoners How a Venture Capital Group Does Scrum Jeff Sutherland, Ph.D., USA Igor Altman, USA Agile /05/191.
The US Oncology Network is supported by McKesson Specialty Health. © 2013 McKesson Specialty Health. All rights reserved. Scrum is an Agile Process.
A4: My Personal Ethos Anna Mirabella April 29,
Cedar Crest College Strategic Planning Community Day.
Melon Yeshoalul From bigger to smaller. A little about me.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
Padma Satyamurthy. 12/12/20152http://lkin15.leankanban.com.
Over Contract negotiation over Processes and tools over Comprehensive documentation overFollowing a plan over.
Introducing Scrum to a New Games Development Studio Harvey Wheaton.
Introduction to Agile. Introduction Who is this guy?
DAKTRONICS LEAN JOURNEY. DAKTRONICS VISION To be the WORLD LEADER at informing and entertaining people through dynamic audio-visual communication systems.
Strategy Mapping Clear path to a successful Agile strategy Dave Neuman Sep 24, 2015 LinkedIn:
Driving to Results: Key Changes and Leadership Behaviors: Management Systems to Deploy & Sustain the Improvements David Munch M.D. IHI Faculty Chief Clinical.
© 2014 IBM Corporation “Leaders Guide to Radical Management” for DevOps with Steve Denning Chapters 6 and 7: From Bureaucracy to Dynamic Linking by Delivering.
1 Chapter 9 Implementing Six Sigma. Top 8 Reasons for Six Sigma Project Failure 8. The training was not practical. 7. The project was too small for DMAIC.
Project Workflow.
Today’s managers & leaders are challenged unlike any of the past generations in their roles.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Human Resource Practices
Data Driven Change When to Steer Towards or Away From Data in Agile Transformations Michael S. McCalla.
Agile Training Day 2 November 17, 2015.
Agile in the Wild The many ways to Apply Agile (not just Scrum and Kanban)
Waterfall, Agile & Scaling Agile
Navigating an Agile Transformation
HR Management for Business Plans
Chapter 3: The Project Management Process Groups: A Case Study
AGILE METHODOLOGY MANAGE PROJECT USING AGILE SCRUM.
Home Page About Us Services Services.
ServiStar Users Group 2018 Advanced Coaching Presented by: Jen Kuhn
Senior leadership – issues and best practices
Our health & wellbeing.
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
Introduction to Agile Blue Ocean Workshops.
Adjective: Able to move quickly and easily. Principles and Values
Building and Sustaining Total Quality Organizations
Scrum Science NGSS: Engineering, Technology, Applications of Science
Randy Knight, MCM Sara Ament Soft Skills for Geeks.
People Lead: This is the visual representation of our model. This model supports and reinforces our definition of leadership - achieving results, with.
Stories of Transformation
Agile, Scrum and CMMI Methodologies
Engaging Senior Executives
Evolving a Continuous Improvement System
What makes a Good Agile Team
AgilityHealth® ScrumMaster Training
Presentation transcript:

Agile Roles in a Flat Organization Kevin Reiter Senior Agile Coach - Geonetric

Introduction Kevin Reiter Kevin.reiter@geonetric.com Started at Geonetric in 2008 Scrum Master Agile Coach CSM, CSPO Adjunct Professor at Kirkwood College and Upper Iowa University Have taught Algebra, Management, Business, Corporate Finance, and Business Math

Geonetric – About us Provide software and services for hospitals and health care providers across the country Around 80 employees Located in Cedar Rapids, IA Been active for nearly 20 years

Geonetric Story Fall 2007 - Scrum training for Engineering team Fall 2011 – Sought out Richard Lawrence (Agile for All) to train us in Behavior Driven Development and Automated Test Driven Development Early 2012 – Manager of Engineering left the organization Summer 2012 – Made the decision to transition our company to “Agile” Fall 2012 – Full company training on all things Agile January 2013 – Started transition to Agile AND removed our traditional management structure

Why take out the managers? Traditionally, there has been some waste built into the job of a manager Agile promotes Self-organizing teams Quarterly Reviews/Performance Appraisals were not worthwhile Brilliant managers, not getting to do what they love

Why take out the managers? All Managers are not Leaders All Leaders are not Managers If we have interesting problems to solve, the work should be it’s own reward (autonomy, mastery, and purpose) Good managers are still an asset to any organization

What happened? Some managers became Product Owners Some people left the organization Some thought this crazy idea would go away after a few months Agile does not mean No Managers We said “How Fascinating!” quite a few times 

Now 2017 is almost over…what did we learn?

How do traditional Scrum Roles factor in? We have Agile Coaches (Relentlessly Focused on Building Great Teams) We have Product Owners (Relentlessly Focused on Delivering Customer Value) We don’t currently have any Scrum Masters (we used to) Every team operates a little bit differently, but we started in the same place

Managers vs. “Managers” vs. Emergent Leaders Many still deferred to the previous Managers for decision making ”You’re not my manager!” Some emerged from within to grab hold of decision making opportunities…and thrived!

People still wanted feedback No managers = no quarterly reviews Moved towards a culture of continuous feedback Giving constructive, honest feedback is HARD for most people Employees wanted an organized structure for receiving and giving feedback

People still need direction and executive leadership Product Owners now got to create backlogs and decide on team priorities How do they know if they are prioritizing the right work? Impact Maps – how does the teams work affect Geonetric’s goals? This required leadership to have a vision and set course for our company

People still wanted to get raises and promotions ”Money is not a motivator!” (Dan Pink, Drive) Autonomy, Mastery and Purpose – the reward is in the work And people like that…but still want to get paid Band Review process – allows employees to grow in their discipline

Who gets to make decisions? What decisions do they get to make? Empowerment to make decisions versus Empowerment to make the RIGHT decisions No manager appointed to make a decision, how does the team decide? Leadership sets boundaries on decision making Levels of Delegation based on subject-matter expertise

Financial and HR literacy Teams control their budgets Employees needed to learn the language of Finance and Accounting Teams are now learning the language of HR Role of the Agile Coach and Product Owner in building great teams

Transparency and Visualization Work is visible on boards, available for group discussion – not locked away on someone’s hard drive Radical Transparency – all information and data is available for employee consumption (short of some confidential HR pieces) “If it’s a problem, make it visible” –Richard Lawrence

What are non-negotiables? All teams must have a Product Owner All teams must have an Agile Coach All teams must work in sprints All teams must hold regular standups, retrospectives and planning sessions

What do you think? Questions? Comments What do you want to know more about?

Thank you!