Scrum, Kanban and other tales

•

2 recomendaciones•816 vistas

The session will cover the most popular agile methods these days. However, my goal isn’t to describe what Scrum or Kanban is and how to introduce them in organizations, but to point what people should take into consideration when choosing the right approach for their team. There is no silver bullet and there is no single universal answer for every issue we face in our project teams. That is why it is so crucial to know what strengths and weaknesses of method of our choice are and what is the specific of the tool we decide to use. Now, which approach would be suitable for your team?

Tecnología Educación

Scrum, Kanban
and other tales
Pawel Brodzinski
@pawelbrodzinski
#jdd

Hi, I’m Pawel and I’m happy to
meet you here
VSoft
http://vsoft.pl

Blog
http://blog.brodzinski.com

Twitter
@pawelbrodzinski

PMSE
http://pm.stackexchange.com/

A story about the old master

http://googletesting.blogspot.com/2010/07/code-coverage-goal-80-and-no-less.html
(and code coverage)
OLD MASTER,
WHAT CODE COVERAGE
SHOULD I AIM FOR?

HM...

A story about the old master
(and agile methods)

LOOK, MY YOUNG APPRENTICE
SOMEONE IS COMING
TO VISIT US

FIRST TEAM LEADER APPROACHES...

OLD MASTER,
WE DO CRAPPY JOB AND
WANT TO DO BETTER.
WHICH METHOD WE
SHOULD USE?
FOCUS ON IMPROVING
YOUR PRACTICES
AND DON’T WORRY ABOUT
METHODS
THANK YOU,
WISE MASTER

SECOND TEAM LEADER APPROACHES... OLD MASTER,
WE DO CRAPPY JOB AND
WANT TO DO BETTER.
WHICH METHOD WE
SHOULD USE?
TELL ME,
WHICH METHOD OUT THERE
IS THE BEST?
THERE ISN’T ONE.
THERE IS NO
SILVER BULLET

EXACTLY!

THANK YOU,
WISE MASTER

THIRD TEAM LEADER APPROACHES...
OLD MASTER,
WE DO CRAPPY JOB AND
WANT TO DO BETTER.
WHICH METHOD WE
SHOULD USE?

USE SCRUM! BY THE BOOK!

THANK YOU,
WISE MASTER

LATER, THAT DAY

BUT MASTER, YOU GAVE
THREE DIFFERENT ANSWERS
FOR THE SAME QUESTION!
WHY?
IT IS A LONG STORY,
BUT LET ME EXPLAIN...

You will get what you want, so don’t
complain to the old master

Thank you
Questions?
Pawel Brodzinski
blog.brodzinski.com
vsoft.pl
@pawelbrodzinski

Más contenido relacionado

Más de Pawel Brodzinski

For years I was telling you how awesome self-organization and autonomy are in the context of organizational design. Well, I lied. Let me share a story about a company that has been a poster child of self-organization and autonomy, bringing them to the extreme and building its organizational culture around them. Everything was as rosy as you might have expected if you'd read books about progressive organizations. That is until it wasn't. The engagement fell flat on its face. The atmosphere nosedived. Attrition crept in. Self-organization, vast autonomy, and radically decentralized control became as much a solution to address the old problems, addressing vastly outdated management principles, as a source of a ton of new friction. We'll look at what went wrong and why. We'll make a sobering realization that making our organizations “fit for the future,” as some management thought-leaders propose, is much harder than it looks on paper. It is a failure story. And a personal one, as I'm going to talk about the company, I've spent almost a decade with – Lunar Logic.

Self-organization: The Good, The bad and the Ugly

Pawel Brodzinski

Recently we get more and more aware of how privilege in society works and how it affects opportunities available to different groups. What we miss out is that a similar power dynamic is in play in the modern workplace. Decision-making power and position in the hierarchy are privileges and they influence how organizations act. Not only does it make companies unprepared for the challenges of the evolving world but also reluctant to change in order to get ready for these challenges. To change the status quo we need to rethink the management models we use in the modern workplace. Interestingly, we know the solution, except we were using it to cure a different disease. Self-organization has been widely adopted in order to improve the performance of our teams. So far, though, we failed to exploit its potential to create the workplace that is more humane, fairer, and most importantly better fit for the future.

Power as Privilege

Pawel Brodzinski

When we talk about effective teams discussions almost always boils down to processes, methods and practices. As a matter of fact, it was the part of our story at Lunar Logic. However, on our evolution toward becoming a company with no managers we uncovered a whole another context to that dispute. Emotional safety is something you’d rather expect to discuss at a psychologist’s couch and not in a professional setup. In modern workplace it is a common expectation that we suppress our emotions. At the same we learned time emotional safety is the superpower that improves problem solving skills, boosts learning, enables feedback, and triggers personal development. However, extremely often it is a blind spot that prevents organizations to get to the next level. Having said that, you can’t just roll out emotional safety just as you introduce a new method or a new tool. Let me discuss what can be done to introduce emotional safety at work and how it transformed us as an organization and as individuals. Ultimately, let me share how it catalyzed effectiveness in individual, organizational and, most importantly, commercial context.

Emotional Safety: The Effectiveness Superpower

Pawel Brodzinski

When we think about self-organization the obvious context is a team. Everyone in the Agile world have heard about self-organized teams. We expect a boost of engagement and productivity when people aren’t told how to organize themselves. Interestingly enough, despite all the benefits we see at a team level, almost no organizations try to scale the concept of self-organization up. The reason is the hierarchical power distribution structure that is at the core of almost all organizations. We commonly call it management. Introducing self-organization throughout the organization would require to redesign how it is managed. Is it even possible? Let me walk you through that story. At Lunar Logic in less than 4 years we evolved from a traditional organizational model with strong management to fully self-organized company. Our CEO has equal access to information and equal decision-making power as an intern who we hired last month. We have no managers and are in need of none. We are not crazy, mind you. The company didn’t collapse. Conversely, the retention has improved, motivation went through the roof, and financially the company has never been more stable as it is now. While I won’t lie that it’s been easy, the outcomes speak for themselves.

A Workplace with No Managers

Pawel Brodzinski

Let me say something obvious. Estimating is hard. So how come that we at Lunar Logic barely remember times when it was an issue? The standard approach to estimation is based on expert guesses. This means that subconsciously we make ourselves vulnerable to cognitive biases which render our estimates too optimistic and unreliable. That neither is fun for development teams nor provides much value to clients. We can employ a different strategy. Instead of relying on vulnerable human memory we use the actual historical data and run statistical simulations to produce a forecast. Not only is the outcome significantly better than what expert guess provides but also it requires less work from development teams. We will share a story how our approach to estimation at Lunar Logic evolved from a common scenario to what we call statistical forecasting. We’ll share the theory behind, show how we do it and present some real data to back up the story. After all, once we understand why estimation is hard we can easily improve how we do it.

Statistical Forecasting: Estimation Made Easy

Pawel Brodzinski

How the idea of collective intelligence affects the way we hire and build teams. It seems that traditional traits we pay attention to doesn't improve capabilities to solve problems, which is at the core of knowledge work. What can we do to improve chances of success of our teams? It seems that social perceptiveness and evenness of communication are way more important than technical skills. There are a few follow up conclusions too...

Collective Intelligence

Pawel Brodzinski

In Pursuit of Happiness

Pawel Brodzinski

We often connect leadership with management. It is a common misconception. On one level – self-organizing teams – we find it rather easy to accept that these are in fact independent concepts. We want the whole team to show leadership and take responsibility for their commitments within the constraints defined by a project, a hierarchy and a method. The same pattern, however, can go way further than that. What would happen if we adopted the same paradigm when designing the whole organization, not just a team? The No Management theme is used to label different approaches that refuse to use traditional management paradigms. While the stories differ one of the common parts is emergence of leadership across organizations on all levels. At the same time I don’t consider No Management a destination. It’s more of a journey and as such it can be used to drive leadership in all sorts of organizations. I will share the story of Lunar Logic, where we evolved from a traditional organization to pretty radical approach where almost everyone is a leader and there’s no formal hierarchy. Some of the ideas are easily applicable on a team level, some require more positional power. All of them are inspiring. It’s not just a story though. I will cover elements of systems thinking, organizational culture, anthropology and psychology that are building blocks that enable such stories to happen in a repeatable manner. Do you want to be a part of one? Join me at this session.

Road to No Mangement

Pawel Brodzinski

Where Would You Like to Work?

Pawel Brodzinski

All the work in our organizations revolves around teams. Teams are a basic unit of structure and thus are ubiquitous. What does differentiate amazing teams from mediocre ones? W. Edwards Deming famously said that "a bad system will defeat a good person every time." By that token the way our teams are organized and the constraints within which they exist are crucial factors behind quality of teams. Let's challenge some of the commonly accepted patterns. High degree of autonomy doesn't turn into anarchy but rather help to keep intrinsic motivation high. Participatory leadership means that every team member is a leader yet it doesn't mean competition. Decisions making process has nothing to do with power structures. Culture is paramount and it goes ahead of technical skills. Collaboration is ultimately the factor the whole team optimizes their work for. These are beautiful teams. Not only are they beautiful but also highly effective, rapidly learning and sustainable.

Beautiful Teams

Pawel Brodzinski

I often hear complaints that we don’t have enough great leaders in our organizations. If, as Jerry Weinberg points, leadership is a process of creating an environment where people become empowered let’s focus on how we create and evolve environments we work at. One issue is the system. W. Edwards Deming famously said that a bad system will defeat a good person every time. Then we should discuss how we build our teams and how it contributes to our goals. Finally, we have organizational culture that is blood of every company and influence all behaviors. All these bits are inseparably interconnected thus if we want to create an environment where leadership thrives we need to take all of them into account. Let’s take a look at how these ideas may be applied in practice. In Lunar Logic eventually but inevitably everyone becomes a leader. We simply pay attention to how the organization is designed in a broader context. That’s the story I will share. After all, there's no shortage of leaders, only a shortage of companies that let leadership emerge.

The Leadership Gap

Pawel Brodzinski

If, as Jerry Weinberg points, leadership is a process of creating an environment where people become empowered let’s focus on how we create and evolve environments we work at. One thing is how we build our teams. If we focus only on technical skills we won’t cover the leadership gap. Another issue is the system. As W. Edwards Deming famously said, a bad system will defeat a good person every time. If we hire great people but put them in highly constrained environment they won’t thrive. Lastly, we have an organizational culture, which is a steering force behind everyday leadership acts or lack of them. It is also one of the main reasons why many transformations fail. I will show how all these areas are inseparably interconnected and how we need to change all three to evolve toward participatory leadership. The end result is that every team member overtakes a role of a leader dynamically, depending on the context. Research on collective intelligence shows how flawed our recruitment approaches are. Experience of system thinkers suggests how much potential is hidden in improving the system. Finally, an organizational culture is what adds meaning to our actions thus is a crucial enabler of change of our behaviors. These are building blocks of the participatory leadership approach. This isn’t just a theory. In Lunar Logic we’ve put this theory into practice. You will learn our story along with why we believe it works. Even though some of the ideas shared during the session may sound counter-intuitive or even radical we are the living proof that it can be done.

People, System, Culture: Where Leadership Thrives

Pawel Brodzinski

The more failed projects and the more underperforming teams I see the more I am convinced that we focus on the wrong things. Neither technical excellence or even a great team is enough to build sustainable organization that delivers and keep its clients happy. The bit we keep forgetting about is organizational culture. The soul of every organization that heavily affects everything that is happening around. It’s not a surprise. For something as intangible there is no recipe, thus evolving organizational culture is never a sure shot. Bear with me when we explore how to tame this fuzzy beast. You may learn why some of your efforts were failing or how to be a better leader or that it’s time to move on and find a new job. Most of all you will understand one more layer of a complex environment we call a workplace

Culture: The Forgotten Bit

Pawel Brodzinski

Building Teams Pecha Kucha

Pawel Brodzinski

One of areas of constant struggle for many organizations is managing portfolio. Too many concurrent endeavors, commitments made without available capabilities, lack of discussion about expected value and cost of delay, disconnection between portfolio management and work organization on team level, constant expediting, highly insufficient or inaccurate information... If any of these sounds familiar it indicates common issues on portfolio level. Interestingly enough, in these areas improvements are rare and traditional models surprisingly prevalent even in organizations that adopt agility across development teams. At the same time very frequently low-hanging fruits can be harvested at PMO level after introducing fairly simple improvements. In this session I will describe how Portfolio Kanban can be used to steer evolution not only at PMO level but across an organization and show how it can be orchestrated with introduction of Lean and Agile on team level.

Fixing Portfolio Management

Pawel Brodzinski

Let’s talk for a while about how we build our teams. Best technical talent that we can find. Good engineering practices. Craftsmanship. Aren’t we full of that stuff? Oh yes, we are. Surprisingly enough that’s exactly the problem. Last time I checked building software has been a team sport. So the question is: what does make a team effective? Once the question is answered we may want to rethink the ways we build our teams.

Building Teams: We Got It All Wrong

Pawel Brodzinski

What pictures do we have in our minds when we think about effective software development? Code quality, continuous integration, pair programming or what have you. While I’m a big fan of all of them I would challenge the concept that this is the only, or the most important, area which developers should focus on. Building software is a collective effort of people working in different roles and this should always be a starting point to a discussion about effectiveness. The missing piece may be software craftsmanship but it may also be handful of dull chores that few would fancy doing. How can we tell? What should we use as guidance? And, at the end of the day, how to build software effectively?

Effective Teams

Pawel Brodzinski

Very frequently, when we discuss a change initiative failure, we point as one of key reasons of the failure lack of support from top management. Much effort on team level is wasted because the organization on high level is set up to preserve status quo. For a change agent looking to set an organization on a path on continuous, evolutionary change addressing the issue of stale mindset of the leaders of the company is frequently the key obstacle to overcome. Usually, a different set of tools is required to achieve that, especially for internal change agents who have hierarchy working against them. I will show how we can use Portfolio Kanban as a low-friction method, which might be used by change agents, to steer mindset change among top managers. Similarly to team-level Kanban a few simple rules help to change how we look at project or product portfolio and how the work flows on high level. Thinking about Kanban on portfolio level introduces the whole new set of challenges that can’t be solved with standard approach, so it is also a story about Kanban versatility and adaptability. After all, if end results include better understanding of how the work is done, improved effectiveness and healthier work environment for teams it is worth giving a try, isn’t it?

Portfolio Kanban

Pawel Brodzinski

When we think about improving effectiveness we often focus on team level. The sources of ineffectiveness, however, are often rooted on a different level - in project portfolio. Too many concurrent projects, little knowledge about available capabilities and lack of discussion on cost and value often result in a situation where main decision factor is a gut feeling. Common approaches to solve the problem are heavy-weight and strongly formalized. On the other hand Portfolio Kanban is a low-friction method that allows tackling the issue steering change at PMO level. As with every Kanban implementation there is little, if any, changes at the very beginning and changes are steered in evolutionary manner. The picture isn’t rosy though. As long as you can say that there are standard approaches to introducing Kanban on a team level, there are no for portfolio level. As long as the method itself is easy to operate, its implementation is going to be anything but obvious and simple.

Portfolio Kanban - Low-Friction Method to Improve Organization's Effectiveness

Pawel Brodzinski

Efficient or Just Busy?

Pawel Brodzinski

Más de Pawel Brodzinski (20)

Self-organization: The Good, The bad and the Ugly

Power as Privilege

Emotional Safety: The Effectiveness Superpower

A Workplace with No Managers

Statistical Forecasting: Estimation Made Easy

Collective Intelligence

In Pursuit of Happiness

Road to No Mangement

Where Would You Like to Work?

Beautiful Teams

The Leadership Gap

People, System, Culture: Where Leadership Thrives

Culture: The Forgotten Bit

Building Teams Pecha Kucha

Fixing Portfolio Management

Building Teams: We Got It All Wrong

Effective Teams

Portfolio Kanban

Portfolio Kanban - Low-Friction Method to Improve Organization's Effectiveness

Efficient or Just Busy?

Último

Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024

The Digital Insurer

Automating Google Workspace (GWS) & more with Apps Script

wesley chun

In this session, we will delve into strategic approaches for optimizing knowledge management within Microsoft 365, amidst the evolving landscape of Copilot. From leveraging automatic metadata classification and permission governance with SharePoint Premium, to unlocking Viva Engage for the cultivation of knowledge and communities, you will gain actionable insights to bolster your organization's knowledge-sharing initiatives. In this session, we will also explore how to facilitate solutions to enable your employees to find answers and expertise within Microsoft 365. You will leave equipped with practical techniques and a deeper understanding of how there is more to effective knowledge management than just enabling Copilot, but building actual solutions to prepare the knowledge that Copilot and your employees can use.

Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...

Drew Madelung

With more memory available, system performance of three Dell devices increased, which can translate to a better user experience Conclusion When your system has plenty of RAM to meet your needs, you can efficiently access the applications and data you need to finish projects and to-do lists without sacrificing time and focus. Our test results show that with more memory available, three Dell PCs delivered better performance and took less time to complete the Procyon Office Productivity benchmark. These advantages translate to users being able to complete workflows more quickly and multitask more easily. Whether you need the mobility of the Latitude 5440, the creative capabilities of the Precision 3470, or the high performance of the OptiPlex Tower Plus 7010, configuring your system with more RAM can help keep processes running smoothly, enabling you to do more without compromising performance.

Boost PC performance: How more available memory can improve productivity

Principled Technologies

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Juan lago vázquez

AWS Community Day CPH - Three problems of Terraform

Andrey Devyatkin

The value of a flexible API Management solution for Open Banking Steve Melan, Manager for IT Innovation and Architecture - State's and Saving's Bank of Luxembourg Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - The value of a flexible API Management solution for O...

apidays

As privacy and data protection regulations evolve rapidly, organizations operating in multiple jurisdictions face mounting challenges to ensure compliance and safeguard customer data. With state-specific privacy laws coming up in multiple states this year, it is essential to understand what their unique data protection regulations will require clearly. How will data privacy evolve in the US in 2024? How to stay compliant? Our panellists will guide you through the intricacies of these states' specific data privacy laws, clarifying complex legal frameworks and compliance requirements. This webinar will review: - The essential aspects of each state's privacy landscape and the latest updates - Common compliance challenges faced by organizations operating in multiple states and best practices to achieve regulatory adherence - Valuable insights into potential changes to existing regulations and prepare your organization for the evolving landscape

TrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments

TrustArc

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

Product Anonymous

Building Digital Trust in a Digital Economy Veronica Tan, Director - Cyber Security Agency of Singapore Apidays Singapore 2024: Connecting Customers, Business and Technology (April 17 & 18, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

apidays

Increase engagement and revenue with Muvi Live Paywall! In this presentation, we will explore the five key benefits of using Muvi Live Paywall to monetize your live streams. You'll learn how Muvi Live Paywall can help you: Monetize your live content easily: Set up pay-per-view access to your live streams and start generating revenue from your content. Increase audience engagement: Provide exclusive, premium content behind the paywall to keep your viewers engaged. Gain valuable viewer insights: Track viewer data and analytics to better understand your audience and tailor your content accordingly. Reduce content piracy: Muvi Live Paywall's security features help protect your content from unauthorized distribution. Streamline your workflow: The all-in-one platform simplifies the process of managing and monetizing your live streams. With Muvi Live Paywall, you can take control of your live stream monetization and create a sustainable business model for your content. Learn more about Muvi Live Paywall and start generating revenue from your live streams today!

Top 5 Benefits OF Using Muvi Live Paywall For Live Streams

Roshan Dwivedi

Scaling API-first – The story of a global engineering organization

Radu Cotescu

This presentation explores the impact of HTML injection attacks on web applications, detailing how attackers exploit vulnerabilities to inject malicious code into web pages. Learn about the potential consequences of such attacks and discover effective mitigation strategies to protect your web applications from HTML injection vulnerabilities. for more information visit https://bostoninstituteofanalytics.org/category/cyber-security-ethical-hacking/

HTML Injection Attacks: Impact and Mitigation Strategies

Boston Institute of Analytics

The Good, the Bad and the Governed - Why is governance a dirty word? David O'Neill, Chief Operating Officer - APIContext Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...

apidays

Axa Assurance Maroc - Insurer Innovation Award 2024

The Digital Insurer

Tata AIG General Insurance Company - Insurer Innovation Award 2024

The Digital Insurer

A Domino Admins Adventures (Engage 2024)

Gabriella Davis

Real Time Object Detection Using Open CV

Khem

presentation ICT roal in 21st century education

jfdjdjcjdnsjd

Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024

The Digital Insurer

Scrum, Kanban and other tales

1. Scrum, Kanban and other tales Pawel Brodzinski @pawelbrodzinski #jdd

2. Hi, I’m Pawel and I’m happy to meet you here VSoft http://vsoft.pl Blog http://blog.brodzinski.com Twitter @pawelbrodzinski PMSE http://pm.stackexchange.com/

3. A story about the old master http://googletesting.blogspot.com/2010/07/code-coverage-goal-80-and-no-less.html (and code coverage) OLD MASTER, WHAT CODE COVERAGE SHOULD I AIM FOR? HM...

4. What can we learn from the story?

5. Hands up...

6. Scrum in a nutshell

7. Kanban in a nutshell

8. A story about the old master (and agile methods) LOOK, MY YOUNG APPRENTICE SOMEONE IS COMING TO VISIT US

9. FIRST TEAM LEADER APPROACHES... OLD MASTER, WE DO CRAPPY JOB AND WANT TO DO BETTER. WHICH METHOD WE SHOULD USE? FOCUS ON IMPROVING YOUR PRACTICES AND DON’T WORRY ABOUT METHODS THANK YOU, WISE MASTER

10. SECOND TEAM LEADER APPROACHES... OLD MASTER, WE DO CRAPPY JOB AND WANT TO DO BETTER. WHICH METHOD WE SHOULD USE? TELL ME, WHICH METHOD OUT THERE IS THE BEST? THERE ISN’T ONE. THERE IS NO SILVER BULLET EXACTLY! THANK YOU, WISE MASTER

11. THIRD TEAM LEADER APPROACHES... OLD MASTER, WE DO CRAPPY JOB AND WANT TO DO BETTER. WHICH METHOD WE SHOULD USE? USE SCRUM! BY THE BOOK! THANK YOU, WISE MASTER

12. LATER, THAT DAY BUT MASTER, YOU GAVE THREE DIFFERENT ANSWERS FOR THE SAME QUESTION! WHY? IT IS A LONG STORY, BUT LET ME EXPLAIN...

13. Inexperienced team

14. Start with basics!

15. Aim for continuous improvement

16. Experienced team

17. Remember about the context

18. Choose the right tools

19. There is no silver bullet!

20. And if you look for a simple recipe...

21. ...than you will get one...

22. ...but will it work?

23. Understand where you are