DevOps Down Under 2011: Lean and Kanban for IT Operations

•

3 likes•1,867 views

The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise stimulates the production of endorphins in the brain which elevate mood and reduce stress levels.

DevOps Down Under 2011: Lean and Kanban for IT Operations

The document discusses Minimum Viable Products (MVP) and Minimum Marketable Features (MMF). It defines an MVP as the minimum version of a product that allows a team to collect validated learning about customers with minimal effort. An MMF is defined as the smallest thing that can be sold or the smallest problem worth solving on its own, that also allows the team to change direction after completion while still providing value. The document provides examples of how to develop an MVP or MMF, such as creating a website or video to gauge interest before coding, or presenting an idea in 5 words to get early feedback.

Tal Aviv - Breaking the vicious cycle in IT Operations using an Agile/Kanban ...

AgileSparks

This document discusses breaking the vicious cycle in IT operations using an Agile/Kanban approach. It begins with a brief history of how IT departments have grown over time from single person departments to specialized groups. This complexity and specialization has led to issues like decreased quality of service, delays, coordination problems between teams, and increased costs. The document then provides an example Kanban board showing how work is currently managed and some of the issues, like requests coming in before their SLA date and missed projected end dates. It concludes by outlining some initial steps that could be taken like defining services and SLAs, establishing flow based on prioritization and coordination, and establishing some basic rules around self-managed teams, reduced multit

Scrum Master Yetkinlikleri

ACM

Product Owner Yetkinlikleri

ACM

The Agile DNA

ACM

The document discusses the key aspects of being agile from the perspective of ACM Software, an agile consultancy company. It emphasizes that being agile means frequently delivering and adapting to changes, creating high-performing cross-functional teams, and focusing on customer delight. It stresses that the secret to achieving agility is focusing on people by empowering them through self-organizing teams and transforming company culture through daily agile practices and values.

Şirket Kimliğini Yaşatabilmek - Poster

ACM

Understanding The Urge To Agility

ACM

The document discusses challenges with traditional waterfall software development approaches and makes the case for adopting agile methodologies. Some key points: - Traditional approaches focus too much on upfront planning and scope definition, which often leads to changes later on that cause delays and missed deadlines. - Agile prioritizes delivering working software frequently in short iterations to get early customer feedback and make adjustments more easily. - Scrum is introduced as a popular agile framework that emphasizes self-organizing cross-functional teams, short development cycles called sprints, and flexibility to change requirements. - A transformation is needed across the organization to shift from traditional command-and-control styles to collaborative agile values like continuous

ACM Agility Services Company 2015

ACM

This document discusses the need for companies to adapt to rapid changes in the world by embracing agile and lean principles. It notes that the world is changing quickly in many areas like technologies, tools, behaviors and organizations. It then highlights research showing that the majority of traditional projects fail or go over budget and time. This emphasizes the importance of being agile to respond to changing requirements and priorities. The document promotes agile methodologies like Scrum, Kanban, and principles of lean and software craftsmanship to help organizations and teams continuously deliver value to customers.

Agility Check-Up is an assessment that evaluates Agile teams and organizations across six perspectives: maturity of roles, teamwork, inspect and adapt processes, transparency, business alignment, and learning organization. Consultants assess each perspective through surveys, meetings, team room visits, and communication to determine maturity levels and identify improvement actions. The assessment aims to help teams and organizations adapt to change and improve their agility.

Scrum Fails?

ACM

This document discusses how Scrum can fail if not implemented properly. It lists behaviors that could lead to Scrum failure, such as not fully understanding Scrum values, changing rules without reason, destroying transparency, ignoring quality practices, and staying away from customers. It emphasizes that success or failure depends on how individuals use Scrum, not on Scrum itself. The document is from an agile consulting company promoting proper Scrum usage.

Product Owner Competency

ACM

Scrum Framework

ACM

Being an Agile Engineer

ACM

Nedir Bu Çeviklik?

ACM

What is Agile - Poster

ACM

Scrum Görsel Kılavuzu

ACM

E twinning Twinspace

Hakan Öztürk

How Agile Are You?

ACM

The document discusses the characteristics of an agile work environment and compares them to a potentially less agile status quo. An agile approach emphasizes face-to-face, open communication among self-organizing collaborative teams; decisions are made as a group while ensuring accountability. Work is done in short cycles with frequent delivery and improvement, customer involvement, and transparency into progress.

Scrum Master Competency

ACM

Agile Manifesto Nedir

ACM

Kanban for Software Development and Kaizen Culture

Acquate

Talk #1 - Kanban for Developers There is much hype about Kanban since it was perfected and introduced to the world by Toyota. Since then, not only manufacturers but all businesses looked into this simple but extremely powerful approach. As software developers are yearning for better project management and visibility on all aspects of their work, Kanban naturally blipped on their radar. In this session, we will look at the origins of Kanban, how it applies to software development along with misunderstandings and myths. We will also compare manufacturing practices with software development techniques and see how we can benefit from their experiences. During the session we will have some interactive exercises to help us better understand Kanban and becoming more efficient and productive by limiting the amount of work we do. Talk #2 - Kaizen: Continuous Process Improvement Enterprises can utilize Process Improvement to improve their workflow, allowing them to be more efficient, eliminate bottlenecks and problem areas, and as a result, achieve reduced costs, on-time delivery and increased profits. Currently, enterprises are facing stiffer competition to win customer acceptance through quality, and the need to develop more customer-oriented products and services faster than ever before. Einstein said "We can't solve problems by using the same kind of thinking we used when we created them.", and that is what lies at the heart of Kaizen. Improvement comes with a different look at the problems and doing this continuously every day and everywhere. It is more of a company culture than a project. But where do we start improving? British comic writer Douglas Adams said "See first, think later, then test. But always see first. Otherwise you will only see what you were expecting.". And that is exactly where we start. By looking deep into our workflow and process. In this session, we will look at Kaizen philosophy, why change is important and very hard to do. we'll also analyze waste and why it is bad for our business and see how quality-first approach makes us better at what we do. I will also provide some test cases and finish off by looking into implementing a Kaizen culture at the office by involving everybody.

Agile (cevik) yaklasim_ile_scrum_yontemi-savas-dogan-cc-by

Savaş DOĞAN

Agile proje yönetimiÖkkeş Emin BALÇİÇEK, MBA

Agile Transformation in Telco Guide

ACM

This guide summaries a successful Agile transformation in Telco with a related case study. Do not take the described steps of this guide as the only way to be successful, there can be many other alternatives for sure. However, this guide explains a way thats experienced to be successful in many companies and under different circumstances. Looking forward to hear your comments & suggestions Thanks

Agile Transformation Governance Model

ACM

Agile Transformation at scale is challenging that requires deep understanding and expertise of agility, discipline and hunger to change. In order to guide you for success in your transformation efforts, we created the Agile Transformation Governance Model. The governance model focuses on 5 key areas together with its 19 sub areas and creates high level of visibility for your transformation efforts.

Agile ve Scrum

Muhammed Özdemir

Sprint Backlog Nedir?

ACM

[Craft Conf 2024] Occupy the Space: A grassroots guide to engineering (and pr...

Jason Yip

The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.

[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...

Jason Yip

[Stretch 2023] We're in it together and other perspectives on effective produ...

Jason Yip

The document outlines Jason Yip's perspective on effective product development culture, which consists of 3 core beliefs, 8 guiding principles, and 9 key practices. The 3 core beliefs are that teams should operate with the mindsets that they are "in it together," people are trustworthy, and performance comes from playfulness. The 8 guiding principles include consent over consensus, autonomy with clear intent, and thinking big while working small. The 9 key practices are aligned autonomous cross-disciplinary teams, test-driven development, continuous delivery, and developing T-shaped individuals.

Viewers also liked

Agility Check Up

ACM

Scrum Fails?

ACM

Product Owner Competency

ACM

Scrum Framework

ACM

Being an Agile Engineer

ACM

Nedir Bu Çeviklik?

ACM

What is Agile - Poster

ACM

Scrum Görsel Kılavuzu

ACM

E twinning Twinspace

Hakan Öztürk

How Agile Are You?

ACM

Scrum Master Competency

ACM

Agile Manifesto Nedir

ACM

Kanban for Software Development and Kaizen Culture

Acquate

Agile (cevik) yaklasim_ile_scrum_yontemi-savas-dogan-cc-by

Savaş DOĞAN

Agile proje yönetimiÖkkeş Emin BALÇİÇEK, MBA

Agile Transformation in Telco Guide

ACM

Agile Transformation Governance Model

ACM

Agile ve Scrum

Muhammed Özdemir

Sprint Backlog Nedir?

ACM

Viewers also liked (19)

Agility Check Up

Scrum Fails?

Product Owner Competency

Scrum Framework

Being an Agile Engineer

Nedir Bu Çeviklik?

What is Agile - Poster

Scrum Görsel Kılavuzu

E twinning Twinspace

How Agile Are You?

Scrum Master Competency

Agile Manifesto Nedir

Kanban for Software Development and Kaizen Culture

Agile (cevik) yaklasim_ile_scrum_yontemi-savas-dogan-cc-by

Agile proje yönetimi

Agile Transformation in Telco Guide

Agile Transformation Governance Model

Agile ve Scrum

Sprint Backlog Nedir?

More from Jason Yip

[Craft Conf 2024] Occupy the Space: A grassroots guide to engineering (and pr...

Jason Yip

[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...

Jason Yip

[Stretch 2023] We're in it together and other perspectives on effective produ...

Jason Yip

[Stretch 2023] What does productivity really mean at different levels_ Indivi...

Jason Yip

Do you want to learn how to boost your productivity at individual, team, and organisational levels? If so, this presentation is for you. Individual productivity is about increased focus, frequent feedback, and reduced friction. Team productivity is about “flow over utilisation” and integration. Organisational productivity is about allocating effort, reducing relearning, and taking parallel bets. By the end of this presentation, you will better understand how to improve productivity at different scales and contexts.

[NYC Scrum] The top 3 points you should have paid attention to in the Spotify...

Jason Yip

The key points from the Spotify engineering culture model that are more important than their structural elements like Squads and Chapters are: 1. Aligned autonomy, which is achieved through a clearly expressed product strategy and empowered product teams. 2. Trust-at-scale, facilitated by cross-pollination between teams and a culture of mutual respect. 3. Decoupling technical services and product capabilities according to their volatility and differentiation. These allow experimentation without blocking other work.

[AgileDevOps West 2023] We're in it together and other perspectives on effect...

Jason Yip

Have you watched those Spotify engineering culture videos? They were trendy and influential in the agile community but that was around nine years ago. What might we say about effective product development culture today? In this keynote, Jason Yip will share a summary of 2023-era effective product development culture based on his eight years at Spotify and 14 years at ThoughtWorks. This will include core beliefs, guiding principles, and core practices. Which ones will align with what you see at your workplace? Which ones will highlight opportunities for improvement? This keynote is not to encourage copying something that will become obsolete in another nine years, but instead to share an example of reflecting on effective product development culture to hopefully encourage your own ongoing reflection and improvement.

[Craft Conf 2023] We're in it together and other perspectives on effective pr...

Jason Yip

Jason Yip presented on effective product development culture. He outlined 3 core beliefs: we're in it together, people are trustworthy, and performance comes from playfulness. There are also 9 guiding principles like consent over consensus and enabling autonomy. Key practices include using aligned, autonomous cross-disciplinary teams, test-driven development, and continuous delivery through research, design, and delivery. The presentation provided perspectives on building an effective culture from Jason's experiences.

[Agile Lean Ireland June 2022] Tactics for influencing leaders at different l...

Jason Yip

[CoPA 2022] Experiences applying BAPO at Spotify.pdf

Jason Yip

[CoPA 2022] Effective Product Development Culture circa 2022.pdf

Jason Yip

[Business Agility Conference 2022] The top 3 points you should have paid atte...

Jason Yip

Agile India 2021: Experimenting with BAPO in Spotify Ads R&D

Jason Yip

BAPO stands for Business Architecture Process Organisation. It is Jan Bosch's more fleshed out expression of "structure should follow strategy". I recently experimented with applying this framework within Spotify Ads R&D and would like to share what worked and what didn't. Concepts expanded beyond BAPO to include product capabilities versus architecture services; overlapping product lifecycle s-curves; Simon Wardley's Pioneers, Settlers, Town Planners; and a reframing of the teaching people how to fish metaphor. Beyond sharing my successes and failures, this session will also encourage attendees to sketch how they might try this framework in their own context and anticipate what issues may appear.

Agile India 2021: 8 guiding principles for Agile Coaches (or change agents)

Jason Yip

The document outlines 8 principles for effective Agile coaching as developed by the Spotify Ads R&D Agile Coaching team. The principles are: 1) Build relationships with both project teams and senior leadership for insight and influence. 2) Focus on long-term systems and habits over short-term wins. 3) Enable others rather than becoming operational. 4) Involve existing leaders in problem-solving. 5) Balance quick wins with addressing underlying issues. 6) Let coaching strategy follow business strategy and needs. 7) Collaboration between coaches is more effective than silos. 8) Intentionally share work to influence change, not just organically.

Frug'Agile 2021: Agile as doctrine (and that's a good thing)

Jason Yip

Using BAPO to apply structure follows strategy

Jason Yip

[Yow! 2019] 3 insights from 4 years at Spotify

Jason Yip

Designing Better Tribe Meetings

Jason Yip

How things still don’t quite work at Spotify... and how we’re trying to solve it

Jason Yip

Agile 2017: What i've learned from 10+ years of evaluating Agile consultants ...

Jason Yip

Agile is mainstream enough that the demand for Agile consultants and coaches is high. High demand attracts many people who lack relevant practical experience or only know how to practice, but don't know how to consult or coach. Organizations need effective ways to filter good candidates from bad. On the other side, candidates want to know what it takes to be considered good. I will share several patterns of selection approaches based on my experiences at Spotify and ThoughtWorks.

What does "speed" mean in software product delivery?

Jason Yip

More from Jason Yip (20)