Agile explained with cars (2018)
•Download as PPSX, PDF•
1 like•620 views
A presentation I gave using car related analogy to explain abit about the agile project methodology alongside with kanban in its parallel use in manufacturing.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Agile explained with cars (2018)
Similar to Agile explained with cars (2018) (20)
Recently uploaded
Recently uploaded (19)
Agile explained with cars (2018)
- 1. (project management) explained with cars agile Sam Ng (#SysOps to #DevOps ) mechanic/^carwash ^automation
- 2. agile defined with context agile / tangkas / 敏捷mǐn jié working together developingsoftware
- 3. agile values Agile manifesto 4 values: 1. People and interactions over processes and tools. 2. Working software over comprehensive documentation. 3. Customer collaboration over contract negotiation. 4. Responding to change over following a plan.
- 4. Agile manifesto 12 principles: agile principles (manifesto) ● Satisfy the customer ● Welcome change ● Deliver frequently ● Work together ● Trust and Support ● Face to face conversation(s) ● Working software ● Sustainable development ● Continuous attention (to technical excellence) ● Maintain simplicity ● Self organising teams ● Reflect and adjust Ref: http://agilemanifesto.org/principles.html
- 5. agile roles Stakeholders - Management - Scrum master (Project Manager) - Product owner - Team Members - Devops Engineer - Customer
- 6. agile
- 7. agile
- 8. agile
- 9. agile
- 10. agile why do we do it TEDx The art of doing twice as much in half the time | Jeff Sutherland
- 11. agile history
- 12. agile roles Stakeholders - Management (CEO etc) - Scrum master (Project Manager) - assists in removing tasks blockers - Assists on Task timelines/sprints planning - Product owner (s) - owns products features/requirements - Balances features against timelines - Developer - Designer(s) - Devops Engineer(s) - Customer(s)
- 13. 1. Conway’s Law(Social side of code) (Applies to API) ○ "Any organisation that designs a system will produce a design whose structure is a copy of the organisation's communication structure." Reference: ● Three Ways Conways Law Affects API Governance ● Social side of your code agile teams
- 14. agile (kanban) flow visualised
- 15. agile visualised 1 Roadblocks (waterfall) vs Spirals (agile)
- 18. Feature vs Product teams (DevOps)
- 20. 1. Any interesting videos recomendations? a. Videos: Insightful/inspiring TEDx talks 1. The art of doing twice as much in half the time | Jeff Sutherland 16mins 2. Agile working: an innovation in the way we work | Anne Cantelo 13mins 3. Agile Leadership: Preparing for an Unconventional Career Path | Emily Phillips 20mins b. Video Channels: Misc Youtube channels videos agile faq
- 21. 2. How to learn about Agile without reading books? #21stcenturylearning Links in my slides in previous slides and below 3. Where can I go to find/learn more? A. Communities (meetups, workshops): ■ Agile Malaysia facebook, peatix ■ Product+ (for Product Owners) facebook, fb events ■ MaGic Cyberjaya (Design thinking etc) facebook, fb events, peatix a. Training & Certification: - Training from Agile Malaysia - Training Centres: Agile Training, Scrum Master training/certification agile faq
- 22. agile (extras) mental toolkit for understanding ● Design thinking ● Systems thinking ○ Surface (events) ○ Patterns/Trends ○ Underlying Structures ○ Mental models/ideas
- 23. agile (extras) mental toolkit for understanding
- 24. agile Any Questions?? Please contact me sam@tehais.com for any feedback. Note: All illustrations and images belong to their copyright holder and is meant for informative purposes only.
Editor's Notes
- Strike out agile -- Rename as - moving fast(er) “together” Sharing to you today “agile” My name is Sam, I am your friendly mechanic and future carwash operator today. We have our friendly designers who work together with the Developers to design our best product = “the mhub car”, we even have a showroom (wait, thats for developers, not us) but dun worry, we have a booth :-p - i am sharing this to you as we move into “Automation”, we understand things at the same level as move together clean up = carwash/ running day to day/existing car shop = mechanic creating a car (implied) = mechanic + engineer (tech) , design (engineering+”art”+aesthetics) - car sales showroom (sales + marketing)
- agile / tangkas / 敏捷 - show picture of athlete (to spur emotions of “agile” feelz) 1) able to move quickly and easily. Ruth was as agile as a monkey synonyms: nimble, lithe, supple, limber, acrobatic, fleet-footed, light-footed, light on one's feet, fleet, lightsome; alert, sharp, acute, shrewd, astute, perceptive, quick-witted 2) software product: relating to or denoting a method of project management, used especially for software development, that is characterized by the division of tasks into short phases of work and frequent reassessment and adaptation of plans. agile methods replace high-level design with frequent redesign
- agile / tangkas / 敏捷 - values Manifesto: a public declaration of policy and aims, - 4 values
- agile / tangkas / 敏捷 - values Manifesto: a public declaration of policy and aims, - 12 principles https://www.knowledgetrain.co.uk/resources/practice/agile-principles
- agile / tangkas / 敏捷 - who roles: Scrum master/Project Manager Product owner Team
- agile / tangkas / 敏捷 - what (?) - applied to working together (software development methods) - waterfall - where development follows a linear path from nailing down requirements to delivery and maintenance, Unclear requirements Requirement changes Lack of involvement of the customers Doubtful accuracy of estimation Uneven loading of the resources Last minute correction is difficult Not much time for testing No time to fix test defects A lot of documentation Schedule and cost overruns Lots of midnight oil burning before final delivery Often the customers are not happy http://www.c-sharpcorner.com/article/agile-methodology-in-software-development-and-drawbacks-of-waterfall-model/ - kanban - If you need to be able to respond to unexpected issues or maintenance stuff, use a Kanban board. A Kanban board is essentially a to-do list that imposes a strict limit on how many work items can be in progress at a given time. It's a great system for keeping your team from getting overwhelmed by interruptions - if an unexpected issue occurs you can prioritise it, but otherwise it goes into the queue.
- agile / tangkas / 敏捷 - what (?) - applied to working together (software development methods) - kanban - If you need to be able to respond to unexpected issues or maintenance stuff, use a Kanban board. A Kanban board is essentially a to-do list that imposes a strict limit on how many work items can be in progress at a given time. It's a great system for keeping your team from getting overwhelmed by interruptions - if an unexpected issue occurs you can prioritise it, but otherwise it goes into the queue.
- agile / tangkas / 敏捷 - what (?) - applied to working together (software development methods) - kanban - If you need to be able to respond to unexpected issues or maintenance stuff, use a Kanban board. A Kanban board is essentially a to-do list that imposes a strict limit on how many work items can be in progress at a given time. It's a great system for keeping your team from getting overwhelmed by interruptions - if an unexpected issue occurs you can prioritise it, but otherwise it goes into the queue.
- agile / tangkas / 敏捷 - what (?) - applied to working together (software development methods) - kanban - If you need to be able to respond to unexpected issues or maintenance stuff, use a Kanban board. A Kanban board is essentially a to-do list that imposes a strict limit on how many work items can be in progress at a given time. It's a great system for keeping your team from getting overwhelmed by interruptions - if an unexpected issue occurs you can prioritise it, but otherwise it goes into the queue. Lean -
- agile / tangkas / 敏捷 - why While agile development is about transparency and cooperation, you still need to protect your time. Here's a few things that you may have heard clients say: - "Can I sit with you so we can work on this together?" - "Can we squeeze in (this huge feature) real quick, it's very small and shouldn't be very hard." - "I have a friend who could do this in a day, could we do this at half price?" - "Can we go back to the first version? Also we shouldn't pay for this if we won't be using the code." These scenarios can cost you a lot of time and money if you don't stand your ground. Your first line of defense is a good project management system. - benefits to tracking your development time (discussed in more length here), but the two main benefits boil down to business intelligence and transparency. - In jargon-free terms, it gives you the ability to make informed plans and to show your clients how much "small changes" really cost in development time.
- agile / tangkas / 敏捷 - history - slide #3 of http://slideplayer.com/slide/6666850/ - Rational Unified Process http://www.mytechnotes.biz/2012/11/introduction-to-rational-unified-process-rup.html https://stackoverflow.com/questions/385511/what-is-the-relation-between-scrum-agile-and-rup - XP https://www.slideshare.net/DamianGordon1/the-extreme-programming-xp-model (focus on pair programing) - scrum history http://agiletrick.com/scrum-history-2/ - https://www.techwell.com/techwell-insights/2012/10/brief-history-scrum
- agile / tangkas / 敏捷 - who roles: Scrum master/Project Manager - assists team members to remove blockages in tasks Product owner - balance the features customer requested, vs product/project delivery, assigns metrics/weightage to tasks DevOps - asssist developers in Continuous Improvement / Continous Delivery in the code/server “pipelines” Team members - designers, developers, admin etc http://www.scaledagileframework.com/product-owner/
- agile / tangkas / 敏捷 - teams https://medium.com/the-ready/how-to-build-your-own-spotify-model-dce98025d32f https://matthewreinbold.com/2017/12/07/ConwayAndAPIDesign/ Communication dictates design The mode of organisational communication is expressed through system design There is never enough time to do something right, but there is always enough time to do it over A task can never be done perfectly, even with unlimited time, but there is always time to complete a task There is a homomorphism from the linear graph of a system to the linear graph of its design organization Homomorphism exists between linear systems and linear organizational structures The structures of large systems tend to disintegrate during development, qualitatively more so than small systems A large system organization is easier to decompose than a smaller one
- agile / tangkas / 敏捷 - why While agile development is about transparency and cooperation, you still need to protect your time. Here's a few things that you may have heard clients say: - "Can I sit with you so we can work on this together?" - "Can we squeeze in (this huge feature) real quick, it's very small and shouldn't be very hard." - "I have a friend who could do this in a day, could we do this at half price?" - "Can we go back to the first version? Also we shouldn't pay for this if we won't be using the code." These scenarios can cost you a lot of time and money if you don't stand your ground. Your first line of defense is a good project management system. - benefits to tracking your development time (discussed in more length here), but the two main benefits boil down to business intelligence and transparency. - In jargon-free terms, it gives you the ability to make informed plans and to show your clients how much "small changes" really cost in development time.
- agile / tangkas / 敏捷 what/why visualised https://www.cirdangroup.com/cirdan-blog/2017/8/30/waterfall-vs-agile-some-differences-to-keep-in-mind
- agile / tangkas / 敏捷 what/why - making a vehicle example Start with the wheels, the base, the car body and add in the steering wheel (only step 4 is a complete product) Agile is characterized by the division of tasks into short phases of work and frequent reassessment and adaptation of plans. -so we start with a skate board, then upgrade to a , bicycle, motorbike, and then 5 = car (each step is a complete usable product) agile methods replace high-level design with frequent redesign (What if people wanted a car in the beginning?)
- https://www.accenture.com/us-en/blogs/blogs-reshma-shinde-devops-transformations-operations
- From DevOps handbook https://caylent.com/devops-handbook-part-2-defining-devops-teams/
- From DevOps handbook https://caylent.com/devops-handbook-part-2-defining-devops-teams/
- agile / tangkas / 敏捷 - FAQ to get learn more without reading a book? Community meetups Youtube videos https://advancetitan.com/news/2016/12/08/tedx-speaker-gives-advice-alternative-career-paths She gave her advice to the audience with her three steps to going down the unconventional career path. “The first step is having an initiative process,” Phillips said. “Number two is my favorite and it’s having a tribe of resources… number three is living outside your comfort zone.” why use cars to explain agile : Relatable Operational narrative - Carwash (manual carwash to automatic machine in petrol stations) - WorkshOP (fixing, tuning, servicing) - Towards Automation for scale
- agile / tangkas / 敏捷 - FAQ to get learn more without reading a book? - Community meetups (tribes) Training & certification Can Agile be applied elsewhere other than software? Marketing : https://www.wrike.com/blog/agile-marketing-buzzword-or-top-strategy-marketers/ Manufacturing : https://www.leanproduction.com/agile-manufacturing.html
- agile / tangkas / 敏捷 - understanding - understanding agile process via systems thinking http://watersfoundation.org/newsletter-archives/march-2014/new-ways-thinking-work/ wHY do i share it, we have so many tools why so hard to integrate https://blog.bluematador.com/posts/how-to-build-your-own-devops-tools-platform/
- agile / tangkas / 敏捷 - understanding - understanding agile process via systems thinking https://www.leylaacaroglu.com/writing-by-leyla//tools-for-systems-thinkers-the-6-fundamental-concepts-of-systems-thinking 1. Interconnectedness 2. Synthesis 3. Emergence 4. Feedback Loops 5. Causality 6. Systems Mapping
- agile / tangkas / 敏捷 - Questions https://www.diygenius.com/the-great-aim-of-education-hebert-spencer/