It&#x27;s not tools, Stupid

Group process by example

Łukasz Aziukiewicz

The document discusses the stages a team goes through in a group process and tips for facilitating effective agile teams. It notes that teams typically go through forming, storming, norming, and performing phases. The tips include building a safe environment for the storming phase, giving the team space to develop norms, and allowing performing once norms are established to reap the benefits of the collaborative team.

Delivering Happiness - The Meddler Game

This document discusses organizational structures that enhance communication within complex organizations. It describes SmartDev, an offshore development center and consulting firm in Vietnam that provides Agile training and coaching. It then profiles two of SmartDev's Agile facilitators, Alexandre Cuva and Hoang Nhac Trung. The document goes on to discuss Agile training offerings and strategies for scaling Agile structures, such as using cross-functional teams, generalizing specialists, and value units to add layers while requiring added value.

Bridging the gap between your Agile project organisation and the traditional ...

Siddhi

This document summarizes the challenges an organization called Exilesoft faced when transitioning to Agile methodology and how they addressed those challenges. Key issues included isolation between project teams and HR, lack of understanding of Agile concepts, and requirements not being clearly communicated. The proposed solution was to improve HR's knowledge of Agile through training and fully implementing Agile practices across the organization. Observing the results, the transition led to improved collaboration, recognition of individual contributions, and an organization-wide performance increase as everyone better understood the new way of working.

Managing Teams

This document discusses various agile methodologies including extreme programming (XP), scrum, lean UX, lean startups, and behavior driven development (BDD). It emphasizes the importance of committed people, flat maintenance costs, delivering quality software frequently, validating business assumptions, and maximizing delivered value. The key aspects of XP, scrum, and lean startup are summarized including roles, meetings, practices, and how they aim to achieve frequent delivery with a focus on the customer and business value.

Implementing Dual-Track Agile :: Lessons from the trenches @ITSpring.by May 2019

Pedro Teixeira

Evermore people are talking about Discovery and Hypothesis-driven approaches. But where do you start? What do they really mean? Pedro will share with us how he moved away from a 2-year delivery roadmap by enabling his Engineering teams to do a Dual Track Agile. A real case-study! Key Learning Points: - Understand what Dual Track Agile is - Learn why Pedro and his team decided to use it at OutSystems - Know what was the strategy in place for the Change Management - Understand their failures and what they have learned with it - Identify some Common Pitfalls - Understand the importance of cadence for alignment and trust - Understand the importance of building (truly) autonomous teams

Business process and inherent waste - Webinar Slides

Ali Zeeshan

This document provides an overview of a webinar on business process and waste. The webinar will be presented by Joseph Micallef on June 1, 2015 from 16:30-17:30 UAE time. Slides and a recording will be made available after. The presenter's background is described. Basic definitions of process are provided, and process review and waste identification are discussed. The eight types of waste - overproduction, inventory, waiting, transportation, over processing, motion, defects, and underutilization of skills - are defined.

Management happiness

Brilyan Product Design - Behind the Scene

Muh Alif Chaeran

The document discusses improvements to Brilyan Product Design's product design process. It notes they transitioned from a waterfall to agile development approach in late 2017. It describes fixing issues like only having 3 designers previously with no standard processes or tools. It details how they now use design thinking and agile principles in the product design phase. It lists achievements like enhancing their mobile workforce and adding new product designers. The overall summary is that Brilyan improved their product design process by standardizing it, growing their team's skills, and satisfying stakeholders and business needs.

Continuous Improvement

[2014] User centered design in practice - a case study from the corporate wor...

WUDnaPRADZE

Scrum

Renny Wijayanti

Scrum is an agile framework that focuses on iterative development through short cycles called sprints. There are three main roles: the product owner prioritizes features and communicates with stakeholders, the development team implements the features, and the scrum master facilitates the process and removes impediments. Key aspects of scrum include daily stand-up meetings to track progress, prioritized backlogs to plan sprints, and retrospectives after each sprint to improve. The goal is to frequently deliver working software and adapt quickly to changes.

Agile Planning: pragmatic approach

Askhat Urazbaev

Agile planning approaches include code & fix, waterfall, and agile. Agile practices like cross-functionality, planning poker, daily scrums, and task boards can help foster teamwork. Case studies describe how agile was applied in an in-house development team, product development company, and support team. Adopting agile principles through rituals rather than just slogans can help teams work better together to meet goals.

How to Find the Right Product Role by Amex Sr. Product Manager

Product Management has a wide range of responsibilities that can depend on the company industry, size of the company, and the expectations of the management team. In this talk, Dan Robinson, Sr. Product Manager at American Express, went over what clues to look for when you're searching for a new product management role. We also discussed the intricacies of how product management roles can differ at companies of 5, 50, and 50,000 employees. Dan talked about what questions to ask during a Product Manager interview, what to look for in responses and how to think about a product role in the greater context of your Product Manager career.

Origins & Overview of Lean and Agile

Georg Fasching

Stc chandan patary_ua_testing _ stc

Chandan Patary

This document discusses ways to improve product development cycles through effective user acceptance testing and engagement. It describes how one organization achieved targets like reducing production to release cycles from 15 to 10 months by having product owners actively participate in validation testing. Stories from the trenches are shared about having product engineers directly involved in validation testing to better represent customer needs. Exploratory "monkey" testing of system boundaries is also discussed. The key takeaway is how design thinking principles were applied, like creating focus groups, prototyping solutions, and getting faster customer feedback through various iterative testing approaches.

Pmp questions and explanations

Venkat Venkat

How to Host a Successful Agile Stand-up Meeting.

Rod Sherwin

The stand-up meeting is considered an important agile practice but why is it so important and how to you get started with this unusual meeting format? When you watch experienced teams run a stand-up, it seems so easy but what are the secret ingredients to hosting a great stand-up meeting? How do you move from the usual 1-hour snore fest status meeting to a short, sharp, engaged, active and valuable ritual? I use the Host Leadership metaphor to help to think about all the aspects needed to run a successful standup meeting.

How to Transition from Engineering to Product by LinkedIn's PM

Management 3.0 Keynote in Agile tour 2013 Hanoi

This document discusses concepts related to agile leadership and motivation. It provides insights from various sources on topics such as self-organizing teams, intrinsic motivation, empowerment, and different leadership styles. References are made to situational leadership theory and its four leadership styles, as well as the seven levels of authority in decision making. The overall message is that empowering teams and developing intrinsic motivation are important aspects of agile leadership.

Measuring the Performance of a Scrum Master

Stephanie Gasche

The document discusses the need for Scrum Masters to measure their performance and impact. It provides 15 potential metrics across three roles of a Scrum Master: facilitator, servant leader, and change agent. Some example metrics include increasing meeting efficiency, improving team happiness, and reducing waste in the organization. The document encourages Scrum Masters to reflect on how metrics can help conversations with stakeholders and facilitate continuous improvement.

Scrum and Agile: Experience growing from 2 to 15 people

Ali Khajeh-Hosseini

- As the startup grew from 2 to 15 people, they implemented Scrum processes like daily standups and sprint retrospectives to improve communication and collaboration across teams. - Key roles like product manager and architect were added to plan features further out while engineers focused on the next 1-2 sprints. - Processes were established for ideas to move from roadmap to development to production, including backlog grooming, epic and sprint planning, and end of sprint demos. Frequent meetings helped align teams working on interdependent features. - Continuous improvement of processes and tools helped support the growing product complexity and multiple teams across timezones needed for large enterprise customers.

CV Andreas Prins Organisation Transformation Coach

Andreas Prins

Andreas is an organizational transformation coach with experience driving Agile transformations at various levels within organizations. He has developed a model called Deep Organizational Transformation (D.O.T.) to guide organizational transformations. As a coach and manager, Andreas has experience guiding management teams, coaching DevOps teams, and facilitating improvements through practices like visual planning, improvement katas, and establishing continuous delivery pipelines.

Understanding Kanban

nikos batsios

Nikos Batsios presents an overview of Kanban principles and practices for managing workflow, including visualizing work, limiting work-in-process, and managing flow. Key aspects covered are using a Kanban board to visualize workflow stages and work items, establishing work-in-process limits to improve throughput, addressing bottlenecks, and helping work flow through the system by reducing waste and handoffs between stages. Metrics like throughput are also discussed. The presentation provides examples and recommendations for applying Kanban principles to optimize an organization's workflow.

7 Must-Try User Experience Tactics For Developers (Tiffany Nolan & Catherine ...

The document provides an overview of 7 must-try user experience tactics for developers: 1) use user stories to understand user needs, 2) sketch designs to explore options before coding, 3) map user flows to optimize tasks, 4) move away from data tables to reduce overload, 5) use whitespace for readability and prioritization, 6) conduct guerrilla testing of 10 minutes to save re-coding, and 7) gather user feedback through the live experience and provide support tools. The document includes examples and explanations for each tactic.

Developer Meet Designer (Andres Galante & Brian Leathem)

This presentation will take developers behind the scenes of the Keynote Demo to showcase how designers and a developers work together to achieve outstanding results. In this presentation, we'll identify the gap between designers and developers, and walk you through an actual example of how to build bridges that increase trust in your products. You'll learn about: - UX basics - Design within open source communities - Understanding the problems between developers and designers - The advantages (and disadvantages) of working with a designer - Coping with common pitfalls and false assumptions - Specific CSS and JS techniques used during the Keynote demo visualization You'll leave knowing that UX goes beyond the UI, with a better understanding of why working with a designer is important, and how to work together successfully.

What's hot

recapitulando: de métodos ágeis até lean startup

Pedro Axelrud

Implementing Dual-Track Agile :: Lessons from the trenches @ITSpring.by May 2019

Pedro Teixeira

Business process and inherent waste - Webinar Slides

Ali Zeeshan

Management happiness

Brilyan Product Design - Behind the Scene

Muh Alif Chaeran

Continuous Improvement

[2014] User centered design in practice - a case study from the corporate wor...

WUDnaPRADZE

Scrum

Renny Wijayanti

Agile Planning: pragmatic approach

Askhat Urazbaev

How to Find the Right Product Role by Amex Sr. Product Manager

Origins & Overview of Lean and Agile

Georg Fasching

Stc chandan patary_ua_testing _ stc

Chandan Patary

Pmp questions and explanations

Venkat Venkat

How to Host a Successful Agile Stand-up Meeting.

Rod Sherwin

How to Transition from Engineering to Product by LinkedIn's PM

Management 3.0 Keynote in Agile tour 2013 Hanoi

Measuring the Performance of a Scrum Master

Stephanie Gasche

Scrum and Agile: Experience growing from 2 to 15 people

Ali Khajeh-Hosseini

CV Andreas Prins Organisation Transformation Coach

Andreas Prins

Understanding Kanban

nikos batsios

What's hot (20)

recapitulando: de métodos ágeis até lean startup

Implementing Dual-Track Agile :: Lessons from the trenches @ITSpring.by May 2019

Business process and inherent waste - Webinar Slides

Management happiness

Brilyan Product Design - Behind the Scene

Continuous Improvement

[2014] User centered design in practice - a case study from the corporate wor...

Scrum

Agile Planning: pragmatic approach

How to Find the Right Product Role by Amex Sr. Product Manager

Origins & Overview of Lean and Agile

Stc chandan patary_ua_testing _ stc

Pmp questions and explanations

How to Host a Successful Agile Stand-up Meeting.

How to Transition from Engineering to Product by LinkedIn's PM

Management 3.0 Keynote in Agile tour 2013 Hanoi

Measuring the Performance of a Scrum Master

Scrum and Agile: Experience growing from 2 to 15 people

CV Andreas Prins Organisation Transformation Coach

Understanding Kanban

Viewers also liked

7 Must-Try User Experience Tactics For Developers (Tiffany Nolan & Catherine ...

Developer Meet Designer (Andres Galante & Brian Leathem)

Agile Is A Four-Letter Word (Jen Krieger)

Based on a wide variety of surveys taken over recent years, many companies are transitioning to something that looks more like Agile than the processes they were using in previous years. However, that transition doesn’t necessarily mean implementations have been done respectfully of the Agile Manifesto and the principles behind it. In large part, industry trends seem to indicate that the sloganization of the word has done a significant disservice to the ideas that were originally founded in 2001. To add even more pain, most people seem to be entirely unaware of the core basis of Agile which is the idea to embrace change but inspect and adapt to that change. Are we lost as an industry? Is there anyway we can recover from this problem? In this session, attendees can expect to engage in a conversation about the rise of the Agile community, the negative and positive impact it has had on the industry, and how you individually can help your organizations and teams lower the risk of encountering the negative problems, and speed your way towards the positives. Topics will include: - The intentions behind agile - Ways you can rework or improve your not so great agile situation - Things you should avoid from the start.

Full Stack Development With Node.Js And NoSQL (Nic Raboy & Arun Gupta)

In this session, we'll talk about what's different about this generation of web applications and how a solid development approach must consider the latency, throughput, and interactivity demand by users across mobile devices, web browsers, and Internet of Things (IoT). We'll demonstrate how to include Couchbase in such applications to support a flexible data model and the easy scalability required for modern development. We'ill demonstrate how to create a full stack application focusing on the CEAN stack, which is composed of Couchbase, Express Framework, AngularJS, and Node.js.

Building Reactive Applications With Node.Js And Red Hat JBoss Data Grid (Gald...

Node.js is a very popular framework for developing asynchronous, event-driven, reactive applications. Red Hat JBoss Data Grid, an in-memory distributed database designed for fast access to large volumes of data and scalability, has recently gained compatibility with Node.js letting reactive applications use it as a persistence layer. Thanks to near caching, JBoss Data Grid offers excellent response times for data queried regularly, and its continuous remote event support means data can get pushed from the data grid to the Node.js application instead of having to wait for the data grid to serve it. In this session, we'll show how to build Node.js applications that use JBoss Data Grid as a persistence layer.

Analyzing Java Applications Using Thermostat (Omair Majid)

Ever wondered how your Java application is actually working? How it's making use of scarce resources on your machine? Ever tried to look under the hood of the Java Virtual Machine (JVM) and felt lost with various tools that don't provide an overall picture, only local details? Thermostat is an open source serviceability tool to help Java developers understand what's happening inside the JVM when their programs are running. Thermostat collects and combines information from various sources—including the Hotspot JVM—to present a complete picture of how the application is behaving. In this session, you'll get a chance to see Thermostat in action as it's used to examine various Java applications, identify what's wrong and fix those problems—often without even modifying the application code. You'll also learn how to add more features to Thermostat through plug-ins. If you're a developer, sysadmin, or QA, and if there's Java in your technology stack, you'll want to learn how Thermostat can make your life easier.

Boost Development With Java EE7 On EAP7 (Demitris Andreadis)

EclipseCon Europe 2016, S. Cela, M.Istria: Eclipse Generic and Extensible Edi...

Mickael Istria

Putting The 'M' In MBaaS—Red Hat Mobile Client Development Platform (Jay Balu...

When you hear the term "MBaaS," or "Red Hat Mobile," there is usually a lot of discussion about powerful scaling, back-end integrations, hosting options, containerization, etc. However, we can't forget what that "M" stands for, and why the platforms exist in the first place, which is to develop and deliver top-notch mobile applications to your users. In this session, we'll review what makes all of this possible—client SDKs, hybrid solutions like Cordova, and Xamarin, and our own Build Farm and Unified Push server. Not stopping there, our AppForms support makes it a snap to tie in back-end systems all the way to your app. And this is all backed by various templates, guides, and new open source resources that will help you get started and join the fun.

Shenandoah GC: Java Without The Garbage Collection Hiccups (Christine Flood)

Just like a spoon full of sugar will cure your hiccups, running your JVM with -XX:+UseShenandoahGC will cure your Java garbage collection hiccups. Shenandoah GC is a new garbage collector algorithm developed for OpenJDK at Red Hat, which will produce much better pause times than the currently-available algorithms without a significant decrease in throughput. In this session, we'll explain how Shenandoah works and compare it to the currently-available OpenJDK garbage collectors.

CDK 2.0: Docker, Kubernetes, And OSE On Your Desk (Langdon White)

Scale changes everything. What once was quite adequate for enterprise messaging can't scale to support "Internet of Things". We need new protocols, patterns and architectures to support this new world. This session will start with basic introduction to the concept of Internet of Things. Next it will discuss general technical challenges involved with the concept and explain why it is becoming mainstream now. Now we’re ready to start talking about solutions. We will introduce some messaging patterns (like telemetry and command/control) and protocols (such as MQTT and AMQP) used in these scenarios. Finally we will see how Apache ActiveMQ is gearing up for this race. We will show tips for horizontal and vertical scaling of the broker, related projects that can help with deployments and what the future development road map looks like.

Write Powerful Javascript Modules To Make Your Apps DRY (Brian Leathem)

Large-scale Javascript applications benefit from a modular approach that let code be reused both within the application and across repeated implementations. In this session, we'll look at the modular approach used to build reusable Javascript modules in the Red Hat mobile field workforce management application (WFM) showcased in this year's Summit middleware keynote demo. Reusable modules for WFM are packaged as node package manager (npm) modules, providing a consistent format for both server and client sides using Node.js and Browserify. Modules are loosely coupled using the Mediator pattern and they broadcast user actions and state changes giving the application and other modules the opportunity to hook into those events. Additionally, visual components are packaged in a framework-agnostic manner, providing reusable UI components. You'll leave this session understanding the challenges faced when building reusable modules for large-scale applications, and the solutions employed in building out the reusable WFM modules.

High Performance Data Storage in a Microservices Environment

Containers: Under The Hood (Vincent Batts)

Despite the popularity and hype of containers, there is no need to regard containers as a block box. It is important to have an awareness of what's going on under the hood to help optimize your container requirements. In this session, we'll discuss: - Namespacing in the kernel - Copy-on-write storage choices - Portable container formats - Available container alternatives - Validation, trust, and content addressability with image verification See examples and options for your use-cases.

MicroServices for Java Developers

The document discusses microservices for Java developers. It introduces Christian Posta, a principal middleware specialist and architect who works with large microservices and is a blogger and speaker on topics like DevOps, integration, and microservices. It then discusses how creating value through software is about speed, iteration, and continuous improvement. It covers concepts like distributed configuration, service discovery, load balancing, circuit breakers, and versioning/routing that are important for microservices. Finally, it mentions container cluster management with Kubernetes and technologies like Kubernetes, OpenShift, and Fabric8 that can help with microservices development.

Building Progressive Web Apps (Kyle Buchanan)

With the recent advancements in modern browsers, more native app-like features are coming to the browser. Things like push notifications, background sync, offline capabilities and home screen app icons have been added to browsers allowing developers to continue building web apps, but now include features that users expect from native apps. In this session we'll take an existing web app and transform it into a progressive web app. We’ll learn how to make the web app installable, how to make it work offline and finally we’ll learn how to add push notifications to re-engage our users.

Kubernetes for Java Developers

By Rafael Benevides and Edson Yanaga Yes, Docker is great. We are all very aware of that, but now it’s time to take the next step: wrapping it all and deploying to a production environment. For this scenario, we need something more. For that “more,” we have Kubernetes by Google, a container platform based on the same technology used to deploy billions of containers per month on Google’s infrastructure. Ready to leverage your Docker skills and package your current Java app (WAR, EAR, or JAR)? Come to this session to see how your current Docker skill set can be easily mapped to Kubernetes concepts and commands. And get ready to deploy your containers in production.

How To Get The Most Out Of Your Hibernate, JBoss EAP 7 Application (Ståle Ped...

The fifth major release of Hibernate sports contains many internal changes developed in collaboration between the Hibernate team and the Red Hat middleware performance team. Efficient access to databases is crucial to get scalable and responsive applications. Hibernate 5 received much attention in this area. You’ll benefit from many of these improvements by merely upgrading. But it's important to understand some of these new, performance-boosting features because you will need to explicitly enable them. We'll explain the development background on all of these powerful new features and the investigation process for performance improvements. Our aim is to provide good guidance so you can make the most of it on your own applications. We'll also peek at other performance improvements made on JBoss EAP 7, like on the caching layer, the connection manager, and the web tier. We want to make sure you can all enjoy better-performing applications—that require less power and less servers—without compromising on your developer’s productivity.

DevOps Moves To Production (Lori MacVittie)

Delivering an app or service fast and frequently to production isn't the same as delivering the app or service fast and frequently to its intended users. Before an app is actually 'live' it has to run the gauntlet of production deployment that stands between it and real, live users. While DevOps has helped organizations make huge strides toward continuous delivery in dev and test environments, the production environment remains a very real obstacle in realizing continuous deployment. The biggest hurdle in that obstacle course is a narrow definition of DevOps that fails to include a broad set of technologies and tools outside the Dev and Ops domain. In this session we'll explore the underlying elements of a comprehensive DevOps approach (SDN, CD/CI, and Agile) and how they mix, match, and combine to enable the operational transformation DevOps promises to achieve the ultimate goal of IT agility: continuous deployment.

Taking Control of Chaos with Docker and Puppet

Puppet

Viewers also liked (20)

7 Must-Try User Experience Tactics For Developers (Tiffany Nolan & Catherine ...

Developer Meet Designer (Andres Galante & Brian Leathem)

Agile Is A Four-Letter Word (Jen Krieger)

Full Stack Development With Node.Js And NoSQL (Nic Raboy & Arun Gupta)

Building Reactive Applications With Node.Js And Red Hat JBoss Data Grid (Gald...

Analyzing Java Applications Using Thermostat (Omair Majid)

Boost Development With Java EE7 On EAP7 (Demitris Andreadis)

EclipseCon Europe 2016, S. Cela, M.Istria: Eclipse Generic and Extensible Edi...

Putting The 'M' In MBaaS—Red Hat Mobile Client Development Platform (Jay Balu...

Shenandoah GC: Java Without The Garbage Collection Hiccups (Christine Flood)

CDK 2.0: Docker, Kubernetes, And OSE On Your Desk (Langdon White)

Write Powerful Javascript Modules To Make Your Apps DRY (Brian Leathem)

High Performance Data Storage in a Microservices Environment

Containers: Under The Hood (Vincent Batts)

MicroServices for Java Developers

Building Progressive Web Apps (Kyle Buchanan)

Kubernetes for Java Developers

How To Get The Most Out Of Your Hibernate, JBoss EAP 7 Application (Ståle Ped...

DevOps Moves To Production (Lori MacVittie)

Taking Control of Chaos with Docker and Puppet

Similar to It's not tools, Stupid

DevOps culture: Computer scientists are only human ... ;)

Jörg Hastreiter

Devops, the future is here it's not evenly distributed yet

Devops, the future is here, but it is not evenly distributed. The document discusses the history and principles of devops. It summarizes that traditionally, development and operations teams had different goals and worked in silos, but devops aims to break down these barriers by advocating for automated testing, continuous integration, infrastructure as code, and cross-functional teams to improve collaboration and speed of delivery. Achieving devops culture and practices can help organizations release changes more quickly, reliably and with higher quality.

August: DevOps 101 (in lieu of DevOps Patterns Distilled)

TriTAUG

The document provides an overview of DevOps from the perspective of Magnus Hedemark. It discusses that DevOps means different things to different people as it is still evolving. To Hedemark, DevOps is about addressing the inefficiencies in the software industry through cultural, process, and organizational changes, sometimes leveraging technology. The document also discusses the concepts of CAMS (Culture, Automation, Measurement, Sharing), Theory of Constraints, Deming Cycle, Toyota Production System, Agile Manifesto, and Kanban as they relate to DevOps.

Devops, Secops, Opsec, DevSec *ops *.* ?

This document discusses the DevOps movement and related concepts. It provides background on how development and operations teams historically worked separately ("Devs vs Ops") and the problems that caused. DevOps aims to break down barriers between teams through practices like automation, continuous integration/delivery, infrastructure as code, and collaboration between teams from the beginning of a project. The document outlines problems DevOps aims to solve and gives examples of tools and approaches for bringing development and operations cultures together.

Devops 101 QA with Kris Buytaert

This document provides an overview of DevOps. It begins with definitions of DevOps, noting that it is a cultural and professional movement, not a new role or team. It discusses how DevOps aims to break down barriers between development and operations teams to improve collaboration. The document outlines some common DevOps practices like automating infrastructure, implementing continuous delivery, measuring metrics, and encouraging sharing of knowledge. It provides examples of how organizations have benefited from DevOps approaches like faster delivery and more stable systems. Overall, the summary emphasizes that DevOps is focused on changing culture and ways of working, not just tools or processes.

Agile 101

beLithe

Learn the basics of the agile way-of-life that has helped many companies realize their potential in the market. The agile secret sauce was once a thing that was only enjoyed by software organizations on the East and West coasts, but is now invading Indianapolis -- increasing productivity, making teams empowered (and happier!), and helping managers focus less on the taskmaster role and more on the important stuff.

Agile Gurugram 2023 I Game Changing Agile: Unleashing a Tectonic Shift in Wor...

AgileNetwork

The document proposes implementing a "Total Football" approach in workplaces to improve team efficiency and drive innovation. It discusses setting goals and planning projects using interchangeable team roles. Key steps include forming a core "Total Football Team" of diverse skills, mapping goals to milestones and rewards, and using a dashboard to provide feedback. The approach is claimed to improve results by decreasing defects while improving morale when used to develop an home automation product.

The lean thinking organization final

Lawell Kiing

This document discusses key concepts of lean thinking and agile practices. It covers the history of lean principles, value thinking over productivity metrics, management focusing on coaching teams rather than command and control, forming cross-functional swarms instead of individual superstars or siloed teams, and how waste reduction can free up capacity equivalent to additional teams. Slack is discussed as necessary for learning and improvement rather than just maximizing output in the short-term. The document provides context around applying lean concepts from manufacturing to knowledge work and software development.

Building High Performance Engineering Teams - Focus on People - Scrum Austral...

Nicholas Muldoon

Twitter has grown from a handful of engineers to over a 1,000 in a few years. To be successful at such a scale requires finding the right people and making sure they are productive and solving valuable customer problems. In this session Nicholas shares the techniques Twitter uses to hire amazing people, unleash their productivity, assess their performance, and improve the flock. Don't miss your chance to see how one of the fastest growing tech companies in Silicon Valley operates and retains the brightest talent.

Devops for drupal

Kris Buytaert gave a talk on DevOps at DrupalCon Munich in 2012. He discussed how the silos between development and operations created problems, and how the DevOps movement aims to break down those barriers through automation, collaboration, and continuous delivery. DevOps is not defined by specific tools but by cultural and process changes like integrating operations work into the entire software lifecycle from early on. The talk covered challenges like managing data and environments across different stages and how tools like Vagrant and configuration management can help address them.

Agile Gurugram 2016 | Conference | Minding the Mind - Agile in an Offshoring ...

AgileNetwork

This document discusses the challenges of implementing Agile methodologies in offshore development environments, where teams are distributed across locations with different time zones and cultures. Key challenges include lack of face-to-face communication, misunderstandings due to cultural and language barriers, and teams not feeling like a cohesive "one team". This can lead to poor productivity, missed deadlines, and delivering solutions that do not provide value. Successful transformations require strong leadership commitment, measuring outcomes differently, and changing organizational structures to promote greater collaboration across distributed teams.

Recruiting for agile teams

Manuele Piastra

Post-Agile Methodologies and all that Jazz

Stojan Peshov

It's been 15 years since the Agile Manifesto was signed and several methodologies were raised ever since. There is almost no developer nowdays that haven't adopted at least one of the Agile principles and uses them in everyday work or even private life. Some has even done improvised versions which work according their needs. The question that's been around these past years is if the Agile is old enough to become past and what's the next big thing, is it a time to call it Post-Agilit period and what that means. What has or needs to change in order to abandon the old and become the Post Agilit followers. Lots of teams already claim themselves as Post-Agilit pioneers and some new ideas of methodologies have been introduced. I'll try to bring an overview of some of them and bring you some thoughts that might help answering the above questions.

Aligning Feature Delivery with OKRs by Gtmhub CPO

The document describes Product School, an online learning platform that offers courses in product management, coding, data analytics, digital marketing, UX design, product leadership, and corporate training. It provides an overview of their course offerings and how they help professionals gain skills in their respective fields. The speaker for the event is then introduced as Jenny Herald, CPO of Gtmhub, who will be discussing aligning feature delivery with OKRs.

Keynote Evento TestingUY 2018 - The Art of Excellence Adding value as an IT p...

TestingUy

Expositor: Derk-Jan De Grood Resumen: In order to distinguish themselves and meet customer expectations organizations need to embrace change. In his keynote Derk-Jan de Grood will explain how Continuous Delivery, DevOps and Scaling Agile aim to effectively react to disruptive innovations, but introduce new challenges. Organization have a need for Visionary’s, Explorers and Experts to make the transition. Develop yourself and your team in order to keep adding value and embrace the new opportunities that arise.

Scrum Deutschland 2018 - Wolfgang Hilpert - Are you agile enough to succeed w...

Wolfgang Hilpert

How do digital innovation and the adoption of Agile methods within the enterprise fit together? What prerequisites are needed to achieve Business Agility? What influence does the leadership culture have on the success of the Agile transformation? What features of a modern leadership role are needed to win in the age of digitization and agility? What does „Leadership Agility“ mean and why is this a critical success factor for the transformation? What do typical hurdles of an Agile transformation look like? How can we measure the success of the transformation?

Tampere goes agile 2015

VincitOy

Why Agile? Back to Basics.

Lucas Hendrich

Reboot your Agile Team - Conference presentation

Martin Lapointe, M.T.I.

Why do so many organizations struggle to put in place mature Agile teams that can apply proper Agile principles and deliver awesome products? Some people will say, “Agile is hard” as an excuse to not do Agile or to become frAgile. Well we think we have developed the “Secret Sauce” to rebooting any Agile team that just doesn’t seem to be maturing and we want to share it with you! If you are thinking of scaling Agile across a large organization, then this talk is a must to attend to help ensure your teams have the right foundation. Organizations wanting to scale Agile must have a solid foundation of mature Agile teams who embrace the Agile values and have the right Agile mindset. Over the years, as we have done Agile transformations in different organizations, we have seen common patterns that keep repeating. The most common pattern we found in our experience is that teams are frAgile. Too many either pretend to be Agile or don’t even know Agile is not a methodology, so organizations question the value of using Agile. Very often the confusion and frustration that comes with thinking that a team is Agile when they are not Agile, brings people right back to their old habits of command and control. Creating successful mature Agile teams is not sorcery, you need to discover the secret sauce! In this talk, we will reveal our secrets on how to create a successful Agile-Scrum team in 5 sprints. Attendees will learn how we applied our secret sauce as we experimented with more than 30 teams and we refined the know-how. This recipe has proven to be successful in different organizations and teams delivering different types of products. Our Creative-Destruction approach goes through a human change process we labeled The Intervention Plan. The 5 steps are: Step 1: Run in the rain Step 2: Thunderstruck Step 3: Start the M&M pain machine Step 4: Open-up and look at the sun Step 5: Removing the training wheels And by using these 5 steps, attendees will discover the 5th Agile value!

How to Reboot Your Agile Team Agile 2017

Maurizio Mancini

This document outlines a method for rebooting an agile team in 5 sprints. It discusses assessing the current state using a survey across 5 dimensions. Sprint 1 focuses on understanding the current problems. Sprint 2 aims to break the status quo and motivate change. Sprint 3 has the team experience pain while implementing changes. Sprint 4 has the team cross the edge and collaborate better. Sprint 5 removes training wheels to create a high performing, self-organized agile team. The method emphasizes the importance of leadership, vision, engagement and quality from the start. It also notes that emotions are part of any change process and should be managed well.

Similar to It's not tools, Stupid (20)

DevOps culture: Computer scientists are only human ... ;)

Devops, the future is here it's not evenly distributed yet

August: DevOps 101 (in lieu of DevOps Patterns Distilled)

Devops, Secops, Opsec, DevSec *ops *.* ?

Devops 101 QA with Kris Buytaert

Agile 101

Agile Gurugram 2023 I Game Changing Agile: Unleashing a Tectonic Shift in Wor...

The lean thinking organization final

Building High Performance Engineering Teams - Focus on People - Scrum Austral...

Devops for drupal

Agile Gurugram 2016 | Conference | Minding the Mind - Agile in an Offshoring ...

Recruiting for agile teams

Post-Agile Methodologies and all that Jazz

Aligning Feature Delivery with OKRs by Gtmhub CPO

Keynote Evento TestingUY 2018 - The Art of Excellence Adding value as an IT p...

Scrum Deutschland 2018 - Wolfgang Hilpert - Are you agile enough to succeed w...

Tampere goes agile 2015

Why Agile? Back to Basics.

Reboot your Agile Team - Conference presentation

How to Reboot Your Agile Team Agile 2017

More from ke4qqq

The Tragedy of Open Source

The document discusses the "Tragedy of the Commons" concept in relation to open source software. It notes that while open source is now the default model for cloud, big data and new technologies, many critical open source projects face underfunding and lack of developer contributions, similar to an overgrazed common field. The document suggests organizations should invest in open source either by paying vendors or contributing code upstream to support core infrastructure projects.

On-demand Continuous Integration with Jenkins, jclouds, and CloudStack

This document discusses using Jenkins, jclouds, and CloudStack together to provide scalable continuous integration testing. It describes how the author transitioned from using dedicated Jenkins masters and VMs to dynamically provisioning build slaves from CloudStack on demand using jclouds. The key steps were building standard images with Packer, configuring the jclouds plugin in Jenkins to integrate with CloudStack as the cloud provider, and configuring jobs to spin up slaves when needed and terminate them after 30 minutes of idle time. This approach provides scalable testing resources that match the varying demand of their many projects.

Cloud Innovation and Risks

This document discusses innovations and risks related to cloud computing and containers. It notes that while public cloud infrastructure services continue growing, the private cloud market has narrowed. It also notes that while infrastructure as a service (IaaS) remains niche for some, operating an internal cloud can erode advantages over public cloud. The document also discusses consolidation in the platform as a service (PaaS) market and risks around building developer communities for open source PaaS projects. It acknowledges security issues with containers and how people consume untrusted container images. Finally, it suggests people are increasingly deploying services using schedulers like Mesos and Kubernetes rather than directly managing virtual machines.

Understanding the CloudStack Release Process

The document discusses the CloudStack release process. It describes the current process which involves feature development, feature freeze, code freeze, and multiple release candidates that cause frustration. The process aims for a 4 month release cycle but has never maintained the schedule. The document proposes moving to reliance on automated testing, more rigid acceptance standards, gated commits based on passing tests, and releasing more frequently with smaller changes to improve quality and reduce delays.

ApacheConEU Keynote: What is the value of the Apache Software Foundation

Ceph and Apache CloudStack

This document discusses using Ceph block storage (RBD) with Apache CloudStack for distributed storage. Ceph provides block-level storage that scales for performance and capacity like SAN storage, addressing the need for EBS-like storage across availability zones. CloudStack currently uses local disk or requires separate storage resources per hypervisor, but using Ceph's distributed RBD allows datacenter-wide storage and removes constraints. Upcoming support in CloudStack includes format 2 RBD, snapshots, datacenter-wide storage resources, and removal of legacy storage dependencies.

Infrastructure as code with Puppet and Apache CloudStack

This document discusses using Puppet to define infrastructure as code with Apache CloudStack. It describes how Puppet can be used to provision and configure virtual machines on CloudStack as well as define entire application stacks. The author provides examples of using Puppet types and providers to define CloudStack instances and groups of instances that can be deployed with a single Puppet manifest. Links are included to learn more about using Puppet to manage CloudStack infrastructure.

DevOps, Cloud, and the Death of Backup Tape Changers

- DevOps aims to break down barriers between development and operations teams through automation, measurement, and culture change. This enables faster delivery of applications and services. - Traditional IT operations has focused too much on control and constraint rather than enabling teams. As a result, developers often work around or avoid IT. - If IT does not adapt by becoming more agile and self-service oriented like cloud computing, it risks becoming irrelevant like backup tape changers - a outdated technology that people work to avoid. IT must partner with teams rather than control them to remain relevant in the future.

Building a Dev/Test Cloud with Apache CloudStack

Building a Dev/Test Cloud with Apache CloudStack

10 Minute Overview of Apache CloudStack

CloudStack is an open source cloud computing platform that allows users to build and manage virtualized cloud environments. It provides tools for provisioning virtual machines, managing networks and storage, and monitoring resource usage. CloudStack's architecture includes components like hypervisors, primary storage, secondary storage, clusters, zones, and a management server. It offers both an administrative web interface and APIs for management and integration.

CloudStack Intro NYC

Infrastructure as code with Puppet and Apache CloudStack

Puppet can now be used to define not only the configuration of machines, but also the machines themselves and entire collections of machines when using CloudStack. New Puppet types and providers allow defining CloudStack instances, groups of instances, and entire application stacks that can then be deployed on CloudStack. This brings infrastructure as code to a new level by allowing Puppet to define and manage the entire CloudStack infrastructure.

Puppet and CloudStack

This document discusses using Puppet and infrastructure as code to manage Apache CloudStack infrastructure. It introduces the cloudstack_resources Puppet module which allows defining CloudStack instances and entire application stacks in Puppet manifests. This enables treating infrastructure like code where Puppet can deploy and configure entire environments on CloudStack. Examples are given of classifying servers and deploying a Hadoop cluster with a single Puppet resource definition. Links are provided to resources for using Puppet with CloudStack and videos that further explain the concepts.

Puppetpreso

This document discusses using Puppet to manage infrastructure as code with Apache CloudStack. It describes how Puppet types and providers were developed to allow defining CloudStack instances and entire application stacks in Puppet manifests. This enables automated deployment and configuration of infrastructure along with software configuration. Examples are given of using Puppet to define CloudStack instances, groups of instances that make up an application stack, and setting defaults for attributes. Resources mentioned include the CloudStack and Puppet GitHub pages.

CloudStack - LinuxFest NorthWest

This presentation provides an overview of Apache CloudStack, an open source cloud computing platform. It discusses CloudStack's history and licensing, its ability to provide infrastructure as a service across multiple hypervisors, and how it enables multi-tenancy, high availability, scalability, and resource allocation. Key CloudStack components and concepts are also summarized, such as networking models, security groups, primary and secondary storage, usage tracking, and its management architecture.

Bacd zenoss

The document discusses several monitoring tools like Nagios, collectd, and Ganglia and notes their lack of automation plugins and APIs. It then introduces Zenoss as a holistic monitoring solution with powerful plugins and APIs that can monitor various cloud platforms, hypervisors, and provide dashboards. Finally, it lists some resources for getting started with Zenoss including documentation, community forums, and code repositories.

Build a Cloud Day - CloudStack

CloudStack is an open source cloud computing platform that provides infrastructure as a service. It was originally formed in 2008 as VMOps and was later acquired by Citrix in 2011. CloudStack allows for on-demand provisioning of computing resources in a multi-tenant environment with high availability and supports various hypervisors including KVM, XenServer, and VMware. It provides APIs to manage and automate the provisioning of virtual computing resources.

Build a Cloud Day - CloudStack

Successfully deploy build manage your cloud with cloud stack2