Fiverr - delivering fast w/ no QA - Agile Israel 2016 Gil Wasserman

Microsoft developer division has implemented SCRUM while developing Visual Studio 2012, and TFS 2012. In this talk we will cover information on this implementation. You will learn about why Microsoft has decided to implement SCRUM, best practices that was helpful for us. How implementing SCRUM has changed our cadence and product delivery cycle. The content will be our developer division SCRUM journey. We are not pure SCRUM put at future leavel we are. I will also discuss which part of our process is SCRUm which part still is not.

Scrum & Kanban - Better Together? Talk delivered at Agile Boston w/ Dave West of Scrum.org in October 2018 It's time to call an end to this stupid civil war within the agile camp. The best agile teams already know that it is not a choice between Scrum and Kanban, but they are complementary. Scrum teams improve when they start to look at flow inside and outside their sprints. Kanban teams improve when they have a disciplined cadence, and effective Product Ownership and Scrum Mastership. In this session, we will look at: Common Ground - The foundations that both approaches highlight Complementary Practices - what can we add from Kanban to our Scrum and vice versa Key differences - where you really need to make a choice Myths - differences that are talked about which really are not there

This document discusses implementing DevOps flow by leveraging lean/agile practices across development, deployment, and operations. It emphasizes establishing continuous integration and delivery workflows to enable frequent, reliable releases through automation. Kanban techniques are presented as a way to visualize work and limit work-in-progress to improve collaboration between teams.

This document proposes an "invitation-based" approach to implementing SAFe that aligns with Lean-Agile principles of respect, decentralization, and flow. Rather than mandating change, it suggests using workshops to invite organizations to consider SAFe and gain alignment. Leaders would be invited to spread SAFe through their areas. Agile Release Train launches would involve an invitation process. The goal is to evolve SAFe's implementation approach by "walking the talk" of its Lean-Agile principles through decentralized decision making and respecting people and culture.

The document compares different approaches for scaling agile, including SAFe (Scaled Agile Framework), LeSS (Large Scale Scrum), and program/portfolio Kanban. It notes that most experts agree teams should only scale when they cannot effectively divide work. When dependencies exist between teams, options include SAFe, LeSS, or using a program/portfolio Kanban approach to visualize work. The document asks questions to help determine the best scaling approach based on factors like guidance needed, agility required, and leadership commitment to change.

In this talk we discuss some of the best practices we have learned for successfully Launching an ART. We discuss how Rational Team Concert (#RTC) can be used to help coordinate the various team activities such as use story analysis, portfolio program and sprint planning, and communicating with the PPM, Agile program and team. The presentation is from the 2015 #ibminterconnect Conference #feggreed2021 DCB-3094 Scaling Agile Launching a SAFe Agile Release Train using Rational Team Concert – Lesson Learned

The document summarizes Pelephone IT's transition to agile methodologies. It describes how Pelephone IT struggled with long development cycles, inability to adapt to changes, and internal blaming cultures. This prompted them to learn agile/Kanban approaches. They started by training managers and developers, then formed cross-functional teams and began regular production releases. This improved time to market, collaboration, and business satisfaction. Moving forward, Pelephone IT aims to refine their agile practices and skills through experience, with an understanding that change takes time and mistakes are expected.

New feature development in agile should almost always start with a spike. Spikes help to define feature scope, uncover technical unknowns, and provide accurate estimates. In this session we will cover how to introduce spikes into your development cycles and show how Atlassian defines spike goals, focuses spike efforts, and makes feature development more effective.

Session "Comparing Ways to Scale Agile" at the Agile Product and Project Manager Meetup in Melbourne, Australia. These days organisations are looking for support to scale their Agile environment. There’s a difference between having one Agile team on its own, or to have several Agile teams providing value to the customer and interacting with each other. This session will give an overview and comparison of all the different Agile scaling approaches out there, i.e.: * Scaled Agile Framework (SAFe) * Evidence-Based Management (EBMgt) * Disciplined Agile Delivery (DAD) * Enterprise Transition Framework (ETF) * Large-Scale Scrum (LeSS) * ScALeD Agile Lean Development * Scaling Agile @ Spotify (SA@S) * Product Development Flow by Reinertsen (PDFbyR)

Introduction to Lean Startup methodology with overview of Vision -> Strategy -> MVP -> Build -> Measure -> Learn -> Cut Waste -> Pivot progression. Fun quizzes and tests explaining concepts like split testing and cohorts. Second part of the presentation goes over how to use Lean Startup in development. Adjusting dev cycle to focus more on learning and to move through the iterations faster. Continuous deployment and production metrics to help move code from the developer to the end user.

The document discusses the benefits of using Rally, an agile test management tool, in software development and testing projects. It notes that agile development is becoming the norm. Rally helps manage requirements, estimation, test case creation, execution, defect tracking, and reporting throughout the agile project lifecycle. It integrates with other tools and provides benefits like real-time status, coordination across teams, and analytics. An example case study describes how Rally was used effectively over multiple sprints in one of Marlabs' client projects to plan, track progress, link defects to user stories, and generate reports.

The document provides an overview of agile software development principles and practices. It discusses benefits of agility such as faster time to market and better responsiveness. Common agile frameworks like Scrum and Kanban are summarized. Extreme programming practices for engineering are outlined. The document also discusses scaling agile through frameworks like SAFe and applying lean principles to software development. Overall it serves as a high-level introduction to agile concepts, methods and roles.

The document discusses various patterns for implementing agile methodologies in distributed teams. It describes structural patterns like local control distributed teams where each site has autonomy over its work, and remote functional teams where different functions are separated by location. It also discusses implementation patterns like remote pairing, virtual collocation, and defining requirements collaboratively through examples.

An introduction to how the Dashlane Engineering Team worked on achieving Continuous Delivery: the ability to deliver to production, fast, reliably and on-demand, through an industrialized automated Release Pipeline.

This document discusses the Essential SAFe framework for scaling agile. It introduces the 10 essential SAFe patterns that should be focused on, which are: Lean-Agile Principles, Real Agile Teams and Trains, Cadence and Synchronization, PI Planning, DevOps and Releasability, System Demo, IP Iteration, Architectural Runway, Lean-Agile Leadership, and Inspect & Adapt. Each element is then explained in more detail over several slides. The document concludes by providing ways Essential SAFe can be used and asking if there are any questions.