Applying the Lean Change Cycle on People: Using Personality to Customize Agile Transformation
Before we change a process we need to understand its current state (Lean Change Cycle described by Jason Little), the same concept applies when trying to change people’s behaviors. Although we hate to admit it, humans are highly predictable. And the more we know about a person, the better our predictions become. This data of course has a wide variety of applications, ranging from targeted marketing campaigns based on demographics (Facebook) to hiring/team building decisions using personality tests (e.g. Myers-Briggs, the Minnesota Multiphasic Personality Inventory, Business Chemistry, and the Enneagram Test). Unfortunately, in regards to agile transformation, we have largely ignored this data, and focused on a logical one-size fits all coaching approach. In this presentation, we will explore the benefits of tailoring guidance and agile coaching strategies based on an individual’s personality.
Outline/structure of the Session
Opening Remarks (5 minutes)
- Discuss the Lean Change Cycle and the standard agile transformation approach (benefits overall waterfall, Scrum training, ad hoc coaching)
- Explain why we need to change and use data to tailor our approach with people
What is Business Chemistry (5 minutes)
- Business Chemistry is a business-oriented behavioral system, co-developed with a team of scientists from the fields of neuroanthropology and genetics.
Understand Yourself - Business Chemistry Personality Types (10 minutes)
- Describe the four personality types: Pioneer, Guardian, Driver, Integrator
- Discuss strategies of engagement
Federal Case Studies (10 minutes)
- Discuss how we adjusted our message based to various leaders at an agile transformation project with a federal agency
Choose your Own Adventure (5 minutes)
- Based on the individual(s) described, how should you go about encouraging them to adopt agile practices and increase their organizations agility
Conclusion (5 minutes)
- Discuss the expected benefits of tailoring your agile transformation approach based on the personality of your clients
Questions & Answers ( 5 minutes)
Understand the traits associated with the four Business Chemistry personality types and how to tailor your agile transformation approach based on your client's personality
Anyone interested in increasing their efectiveness
schedule Submitted 1 month ago
People who liked this proposal, also liked:
End to End Kanban for the Whole OrganizationColleen Johnson
schedule 1 month agoSold Out!
IntermediateWe often look to our engineering teams first to drive efficiency and speed to deliver but as we optimize the flow of our development processes we quickly create pressure in the organizational workflow with the activities that feed into and out of product delivery. Product definition struggles to keep pace and establish a queue of viable options to pull from. Marketing efforts begin to pile up as features release faster than we can share the news. All of this stems from optimizing only one part of the overall system. In this talk we will look at how to scale Kanban practices to the entire organization to provide the visibility, flexibility and predictability to make every part of the business truly agile.
Agile Transformation at the IRS: What Ken Schwaber didn’t teach us
In the 1040 environment of strict compliance, frequent audits and heavy penalties, the IRS has been pursuing the adoption of agile practices in order to realize faster project delivery that also result in better quality products. We now have bright spots throughout the enterprise, but getting here was a journey in which we had to adapt the traditional teachings of Scrum to the IRS culture. In this presentation, we will discuss the agile transformation journey of the IRS and provide the audience with a transformation framework that accounts for our lessons learned in a bureaucratic organization
Cultivating Agile Practices in the Midst of Bureaucratic Procedures
Federal agencies have been increasingly urging projects to use agile practices to produce higher quality products faster. Unfortunately, the culture and established processes (e.g. Waterfall) hinder the adoption of agile practices. In this presentation we will talk about how we were able to give Agile projects more autonomy and get around a Change Request Process that required a 2 month approval cycle for any change to user stories