Agile Organizational Design & Kanban Flow · & Kanban Flow Organizational Design is a critical step in the overall Agile transformation and successful adoption. Dimitri shares his
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Organizational Design is a critical step in the overall Agile transformation and successful adoption. Dimitri shares his vast experience to illustrate how organizations can structure themselves to get the most benefit from being Agile and Lean. This presentation focuses on flowing work effectively using an Agile Canvas (i.e.:Organizational Design) and leveraging Kanban boards to ensure transparency/accountability at all levels of the organization. Once we master setting up the ideal organizational structure, we will explore actual Kanban board examples to visualize the flow of work across the organization. Ultimately, it’s all about connecting clear goals, with meaningful features and well written stories; while reducing dependencies and creating simple communication channels. You will walk away with real examples and techniques that you can implement immediately within your organization.
About Dimitri PonomareffDimitri Ponomareff (www.linkedin.com/in/dimka5) is a Coach. Whether it's a sports team, software products or entire organizations, Dimitri has that ability to relate and energize people. He is consistently recognized as a very passionate and successful change agent, with an overwhelming capacity to motivate and mobilize teams on their path to continuous improvements. He is a master facilitator, as well as a captivating speaker with consistent, positive feedback regarding his ability to engage an audience.
As a certified Coach, Project Manager and Facilitator of "The 7 Habits of Highly Effective People", Dimitri brings a full spectrum of knowledge in his delivery of methodologies. Through teaching by example, he is able to build teams of people who understand where to focus their work to generate the most value.
He has coached and provided tailor-made services and training for a multitude of organizations. The short list includes, American Express, Charles Schwab, Bank of America, Morgan Stanley, Best Western, Choice Hotels, JDA Software, LifeLock, First Solar, Infusionsoft and Mayo Clinic. Dimitri enjoys his work, and does everything to ensure he shares his knowledge with others who seek it.
Post-design WorkflowOrganizational design is a step-by-step methodology which identifies dysfunctional aspects of workflow, procedures, structures and systems, realigns them to fit current business realities/goals and then develops plans to implement the new changes.
over comprehensive documentation● Customer collaboration
over contract negotiation● Responding to change
over following a plan
1. Satisfy the Customer 2. Welcome Change3. Deliver Frequently4. Work as a Team 5. Motivate People6. Communicate Face-to-Face7. Measure Working Software8. Keep a Sustainable Pace9. Excel at Quality
10. Keep it Simple11. Self-Organize12. Reflect and Adjust Regularly
Lean
1. Eliminate waste2. Amplify learning3. Decide as late as possible4. Deliver as fast as possible5. Empower the team6. Build quality in7. See the whole
“Organizations that are truly lean have a strong competitive advantage because they respond very rapidly and in a highly disciplined manner to market demand, rather than try to predict the future.” – Mary Poppendieck
Build the right thing: Understand and deliver real value to real customers. Build it fast: Dramatically reduce the lead time from customer need to delivered solution. Build the thing right: Guarantee quality and speed with automated testing, integration and deployment. Learn through feedback: Evolve the product design based on early and frequent end-to-end feedback.
"Just-in-Time" means making "only what is needed, when it is needed, and in the amount needed."Source: http://www.toyota-global.com/company/vision_philosophy/
Throughput is about performance…Throughput is based on actual data to represent the number of cards delivered in a given period of time on a specific Kanban board.
Cycle Time is about responsivenessCycle Time is calculated from the time a card is worked on by the team until the time the card is delivered. In simple terms, it’s how long a card stays within the Work-In-Progress (WIP) columns of your board.
This presentation was inspired by the work of many people and we have done our very best to attribute all authors of texts and images, and recognize any copyrights. If you think that anything in this presentation should be changed, added or removed, please contact us.