Lean and Kanban Principles for Software Developers

•Download as KEY, PDF•

2 likes•2,402 views

This was a presentation given for the South Florida Code Camp in March, 2010 covering the basics of Lean and Kanban principles for Software Developers

Technology

LEAN, KANBAN, AGILE
@cory_foy | Cory Foy | http://coryfoy.com

Waterfall
Requirements

Design

Development

Waterfall
Requirements

Design

Development

Test

Waterfall
Requirements

Design

Development

Test

Credit: http://www.ﬂickr.com/photos/tonymangan/611780383

Agile
Waterfall Agile
70

52.5

35

17.5

0
Q1 Q2 Q3 Q4 Q5 Q6

Scrum
Ideal Actual
100

75

50

25

0
1 2 3 4 5 6 7 8 9 10

Credit: http://www.ﬂickr.com/photos/shellysblogger/2464975037/

Goodness
More
Lines of Code

Great
Developer

More
Bugs Found
More Goodness

Awesome
Tester

More
Sales More Money

Happy Customers

Company

More
Sales More Money

Happy Customers

Happy
Company

More
Sales More Money

Happy Customers

Happy
Company

Happy Developers

Waiting Development Test

Feature 1 64-Bit
Priority Bug 2 Testing
Bug 17
Feature 11
Priority Bug 7

Feature 18
Bug 4

Feature 42

Waiting Development Test

64-Bit
Testing

Feature 1
Priority Bug 7
Priority Bug 2
Feature 18 Bug 17
Feature 11
Bug 4

Feature 42

Waiting Development Test
Priority Bug 7
64-Bit
Feature 18
Testing
Bug 4
Feature 42

Feature 1
Priority Bug 2
Bug 17
Feature 11

Waiting [8] Dev [4] Test [2]

Feature 1 64-Bit
Priority Bug 2 Testing
Bug 17
Feature 11
Priority Bug 7

Feature 18
Bug 4

Feature 42

Waiting [8] Dev [4] Test [2]

64-Bit
Priority Bug 2 Testing
Bug 17 Feature 1
Feature 11
Priority Bug 7

Feature 18
Bug 4

Feature 42

Waiting [8] Dev [4] Test [2]

Priority Bug 7 64-Bit
Priority Bug 2 Testing
Bug 17 Feature 1
Feature 11

Feature 18
Bug 4

Feature 42

Seven Principles

Decide as late as
possible

Seven Principles

Deliver as fast as
possible

Understand Your Existing Process

Value Stream Map

Customer Enters Bug to
Emails Rep Tracker

Customer Enters Bug to Executive
Emails Rep Tracker Review

Customer Enters Bug to Executive
Emails Rep Tracker Review

Assigned Fix
in Version

Customer Enters Bug to Executive
Emails Rep Tracker Review

Assigned Fix Assigned to
in Version Dev Team

Customer Enters Bug to Executive
Emails Rep Tracker Review

Assigned Fix Assigned to
Coded
in Version Dev Team

Customer Enters Bug to Executive
Emails Rep Tracker Review

Assigned Fix Assigned to
Coded
in Version Dev Team

Assigned to
Test Team

Customer Enters Bug to Executive
Emails Rep Tracker Review

Assigned Fix Assigned to
Coded
in Version Dev Team

Assigned to
Tested
Test Team

Customer Enters Bug to Executive
Emails Rep Tracker Review

Assigned Fix Assigned to
Coded
in Version Dev Team

Assigned to Release
Tested
Test Team Planning

Customer 1 Enters Bug to 1-2 Executive
Months
Emails Rep Week Tracker Review
1 Day

Assigned Fix 3 Assigned to 2
Weeks Weeks Coded
in Version Dev Team
1 Day

Assigned to 1 4 Release
Week Tested Weeks
Test Team Planning
2 Days

Deploy to 1 1 Deploy to
Week Tested Week
Beta Site Production

Reduce Waste -> Seven Wastes

Partially Done
Work

Reduce Waste -> Seven Wastes

Extra Features

Reduce Waste -> Seven Wastes

Lost Knowledge

Reduce Waste -> Seven Wastes

Task Switching

Reduce Waste

Single Responsibility Principle

SOLID

Reduce Waste

Single Responsibility Principle

SOLID
Open-Closed Principle

Reduce Waste

Single Responsibility Principle

SOLID
Open-Closed Principle

Liskov Substitution Principle

Reduce Waste

Single Responsibility Principle

Interface Segregation Principle

SOLID
Open-Closed Principle

Liskov Substitution Principle

Reduce Waste

Single Responsibility Principle

Interface Segregation Principle

SOLID
Dependency Inversion Principle

Open-Closed Principle

Liskov Substitution Principle

Reduce Waste

TDD
Test-Driven Development

Reduce Waste

Behavior-Driven Development

TDD
Test-Driven Development

Reduce Waste

Behavior-Driven Development

TDD
Test-Driven Development

Acceptance-Test Driven Development

•Cory Foy
•Slides at: http://coryfoy.com
•Email: foyc at cory foy dot com
•Twitter: @cory_foy

This document discusses how Kanban can be used to facilitate evolutionary organizational change. It describes Kanban as a change management system that uses visual boards and limits on work-in-progress to provoke incremental, continuous improvement. The document provides examples of how visualizing workflow and restricting work-in-progress can help align teams and processes, overcome resistance to change, and establish a culture of continuous learning.

Agile - Iteration 0 CodeMash 2010

kensipe

The document discusses the purpose and activities of Iteration 0 in an agile development process. It describes setting up key infrastructure items like version control, IDE configuration, build systems, continuous integration, and project management tools. It emphasizes automating as many tasks as possible. The goal of Iteration 0 is to establish the foundation for subsequent iterations by creating a stable development environment and processes.

Beyond Scrum: Scaling Agile with Continuous Delivery and Subversion

Product Marketing Services

Real Developers Don't Need Unit Tests

John Ferguson Smart Limited

Introducing Obsidian Software and RAVEN-GCS for PowerPC

DVClub

Marrying Jenkins and Gerrit-Berlin Expert Days 2013

Dharmesh Sheta

The document discusses marrying Gerrit and Jenkins to improve the code review process. Gerrit is a widely used Git server and code review tool. Jenkins is a popular open source continuous integration tool. By connecting Gerrit and Jenkins, developers can ensure code review requests meet quality standards before review by having Jenkins automatically build and test code changes and report the results in Gerrit. This allows code review to focus on design and avoids wasted time on requests that fail builds or tests. The document then demonstrates this workflow with Gerrit and Jenkins.

Release planning

Oleg Seriaga

How we build quality software at uSwitch.com

hemalkuntawala

The document describes uSwitch's process for developing quality software. It outlines how the company has evolved from a traditional waterfall approach to a more agile, test-driven development model focused on: 1. Building quality into software from the start rather than relying on inspection and testing later. 2. Having testers work alongside developers to continuously test software throughout development. 3. Conducting demonstrations and sign-offs on demand from business stakeholders to obtain early feedback. The process emphasizes continuous testing, monitoring of production systems, and breaking work into individually deployable tasks to enable rapid, flexible development and deployment of high quality software.

Refactoring is altering the internal structure of code without changing its external behavior or functionality. It improves code quality by enhancing readability, maintainability and extensibility. Successful refactoring requires knowledge of the codebase, a structured API, and unit testing. Refactoring can be done continuously or in scheduled chunks, and should be performed by those familiar with the code. Tips include writing tests first, using documentation, and avoiding full reliance on IDE refactoring tools.

Continuous deployment

Daniel

The document discusses best practices for continuous integration, continuous delivery, and automation in software development. It recommends automating the entire development cycle from build to test to deployment. Changes should be deployed frequently, such as multiple times a day, to catch errors early. All code, configurations, and dependencies should be stored in version control. A deployment pipeline approach is advocated with separate stages for testing, verification, and release to different environments. Rollback and recovery should be planned and tested.

Teams progress presenation

Oleg Seriaga

Pair Programming

Naresh Jain

This document discusses pair programming, which involves two programmers working together on the same design, algorithm, code, or test. The benefits of pair programming include improved quality through continuous review, less defects through early detection, improved problem solving abilities, and higher productivity through less distraction. Pair programming also leads to better learning, team communication, and risk mitigation. Challenges include difficulty convincing stakeholders and dealing with strong individual code ownership. The document provides examples of pairing techniques and tips to implement pair programming successfully.

Continuous Testing

jaredrrichardson

CI in the mobile world

Godfrey Nolan

This document discusses continuous integration (CI) for mobile applications. It defines CI as automating the entire development process including building, testing, and deploying software. The benefits of CI for mobile include fewer errors, faster feedback, and no manual testing required. It also discusses configuring CI for both Android and iPhone projects, including using a CI server like Jenkins, source code repositories, building and running unit/functional tests on emulators or devices, and deployment options like emailing APKs or using TestFlight.

Software reengineering for Developers

Bradley Irby

Evolution Of Team Interaction Models

Naresh Jain

Blue Monitor Software Development

urbantech

Blue Monitor Systems is an employee-owned company dedicated to delivering high-quality creative, technical, and scientific services worldwide. The company encourages employees to think like owners and contribute to social well-being. Blue Monitor uses an iterative "Zero Time" method combining Agile and traditional approaches for medium and large projects. This includes continuous integration, test-driven development, and matrix project teams with specialists in design, engineering, testing, and operations.

Real World TDD

Schalk Cronjé

The document discusses real world test-driven development (TDD). It addresses several myths about TDD, such as that it only involves writing unit tests before code or is only for new code. The document advocates for writing tests at multiple levels, including unit, integration, and deployment tests. It also emphasizes that test code quality is important and recommends integrating developers and testers, building walking skeletons before features, and using continuous integration practices. The overall message is that there are different ways to approach TDD effectively in the real world.

Apache Deltaspike the CDI Toolbox (Java One 2015)

Antoine Sabot-Durand

Test Strategy

Zbyszek Mockun

Releasing fast code - The DevOps approach

Michael Kopp

Agile makes you Develop faster, DevOps also makes you Deploy faster but how do you make your Application faster? Many currently used Performance Management practices don’t work anymore as they are too time consuming. It takes a new approach to track performance in Continuous Integration, get more value out of Load Testing and leverage production data for performance optimization. We will show you real world examples on how the new DevOps approach can work.

PowerPoint Presentation

rhofkens

Continuous delivery (CD) allows software updates to be released frequently by having each code change trigger automated builds, tests, and deployments. This document discusses best practices for implementing CD for Alfresco solutions, including using consistent project templates built with Maven or Gradle, packaging modules as AMPs, externalizing configurations, supporting multi-module deployments, using deployment frameworks like Chef, and deploying to test instances on private clouds. Common pitfalls to avoid are unrealistic time planning, lack of involvement from system admins, and developers not understanding the importance of green builds.

Why Test Driven Development?

Naresh Jain

The document discusses test-driven development (TDD) and the benefits of automated unit testing. It describes the TDD rhythm of adding a test, seeing it fail, making the minimal code change to pass the test, then refactoring. TDD helps produce maintainable, loosely coupled code by focusing on writing tests first, catching errors early, and communicating design decisions. The goals of TDD include making programming more enjoyable, understanding code easily, and reducing maintenance costs significantly.

Beyond Kanban: Lean Thinking for Agile Teams

avpereira

The growing interest about Kanban in the Agile Community seems to reduce learning about Lean Thinking to one principle only: PULL. This talk was prepared for the Agile PT 2011 conference and provides an overview of the 14 Management Principles for developing a Lean Culture and how IT frameworks such as SCRUM or KANBAN for Software Development apply them. It introduces Lean Leardership and People Development principles as well as fundamental Lean Practices beyond kanban such as Value Stream Mapping, Continuous Flow, Leveling (Heijunka), Stop and Fix (Jidoka), Visual Standards, Visual Controls and A3 Problem Solving. Knowledge about these often overlooked principles and practices will help agile teams to see the whole and better understand the lean concepts behind agile frameworks such as SCRUM and KANBAN. They will be better equipped to create learning and adaptive organizations by solving problems in the implementation of agile frameworks instead of spending time discussing which framework is better. After all, the goal is to "be lean and agile" and not to "do Lean" or "do Agile"

Masaaki imai and total quality management

vishwa3gk

Masaaki Imai developed the concept of Kaizen, or continuous improvement, which is a central tenet of Total Quality Management. Kaizen promotes continuous small improvements made by all employees to optimize processes. It focuses on process improvement and stresses that success relies on empowering employees through discipline, participation, skills development, and communication. A key principle of Kaizen is maintaining a constant sense of urgency to improve quality without becoming complacent.

Agile Software Development Overview

sunilkumar_

This document provides an overview of agile software development. It discusses the differences between the waterfall model and agile approaches. The key principles of agile include prioritizing individuals and interactions, working software, customer collaboration, and responding to change. An example agile process used by Elsevier is described, involving roles like product owners, business analysts, developers, and quality analysts. Extreme programming is mentioned as an agile method that focuses on user stories, small releases, pair programming, unit testing, and simplicity.

Hoshin kanri and the x matrix small

christiannah

Hoshin Kanri is a method for controlling the direction of a company or project. It involves aligning objectives across all levels of an organization from corporate goals down to specific tasks, and monitoring progress through monthly reviews. The X-matrix is a tool used in Hoshin Kanri that ties all the objectives and initiatives together in one place, allowing everyone to manage progress collectively and ensure alignment.

Manufacturing wastes

Mohamed EL-Sayed

This document discusses the concepts of value, waste, and lean manufacturing. It defines value-added activities as those that directly change a product to meet customer needs, while non-value added activities are necessary but do not increase value. The main types of waste are identified as muda (non-value added work), mura (unevenness), and muri (overburdening work). Specific examples of muda include transportation, inventory, motion, waiting, overproduction, overprocessing, and defects. The document emphasizes that eliminating waste through lean principles can improve flow and reduce costs for companies.

What's hot

TMF2014 CI-CD Workshop Michael Palotas

KJR

Agile Evolution with Kanban

Chris McDermott

The Power Of Refactoring (PHPCon Italia)

Stefan Koopmanschap

Continuous deployment

Daniel

Teams progress presenation

Oleg Seriaga

Pair Programming

Naresh Jain

Continuous Testing

jaredrrichardson

CI in the mobile world

Godfrey Nolan

Software reengineering for Developers

Bradley Irby

Evolution Of Team Interaction Models

Naresh Jain

Blue Monitor Software Development

urbantech

Real World TDD

Schalk Cronjé

Apache Deltaspike the CDI Toolbox (Java One 2015)

Antoine Sabot-Durand

Test Strategy

Zbyszek Mockun

Releasing fast code - The DevOps approach

Michael Kopp

PowerPoint Presentation

rhofkens

Why Test Driven Development?

Naresh Jain

What's hot (17)

TMF2014 CI-CD Workshop Michael Palotas

Agile Evolution with Kanban

The Power Of Refactoring (PHPCon Italia)

Continuous deployment

Teams progress presenation

Pair Programming

Continuous Testing

CI in the mobile world

Software reengineering for Developers

Evolution Of Team Interaction Models

Blue Monitor Software Development

Real World TDD

Apache Deltaspike the CDI Toolbox (Java One 2015)

Test Strategy

Releasing fast code - The DevOps approach

PowerPoint Presentation

Why Test Driven Development?

Viewers also liked

Beyond Kanban: Lean Thinking for Agile Teams

avpereira

Masaaki imai and total quality management

vishwa3gk

Agile Software Development Overview

sunilkumar_

Hoshin kanri and the x matrix small

christiannah

Manufacturing wastes

Mohamed EL-Sayed

Identifying Waste

Operational Excellence Consulting

The current global recession driven by COVID-19 has literally brought sales to a halt for many businesses. Compounded by high labour and material costs and unsold inventory, it is difficult to sustain your businesses without dramatic cost reductions. Before cutting salaries and laying off staff, now is the right time to seriously take a hard look at how you can quickly and systematically discover waste in your business processes and eliminate them so as to sustain a positive cash flow. This presentation teaches you how to discover waste. Waste are all around us, and they include all those extraneous and counterproductive assumptions, attitudes, activities, materials, machines, operations and processes. This presentation can be used to educate your management and staff on the four models that can be used to systematically discover waste on the shopfloor. To be able to discover waste is the first step towards its elimination. This training material can also be used to supplement your Lean Manufacturing, Gemba Walk, Kaizen, 5S and TPM training materials. LEARNING OBJECTIVES: 1. Discover waste in your work environment 2. Learn how to remove waste 3. Learn how to prevent waste CONTENTS: 1. What is Waste? What is Value? What is Value-added? What is Waste? How Does Waste Take Root? Waste Take Root When We Accept Stopgap Improvement Benefits of Identifying & Eliminating Waste 2. The Classification of Waste The Three MUs The 5M + Q + S The Flow of Goods The Eight Types of Waste 3. How to Discover Waste Three Approaches to Discover Waste Using the Back Door Bringing Latent Waste to the Surface Analyzing Current Conditions Value Stream Mapping Value-added Flow Chart Flow Analysis Chart 4. How to Remove Waste Adopt the Necessary Attitude Remove Waste in the Movement of Goods Remove Waste in the Actions of People Remove Waste in the Way People, Goods and Machines Are Combined 5. How to Prevent Waste Standardization Visual Controls Auditory Controls 5W + 1H To download this complete presentation, please visit: http://www.oeconsulting.com.sg

Improvement Kata Workshop

W3 Group Canada Inc.

This document provides an introduction and agenda for a Toyota Kata workshop presented by Marek Piatkowski. The workshop will cover the Improvement Kata and Coaching Kata routines used by Toyota to develop continuous improvement capabilities. It will include a team exercise applying the Kata routines to a quality test lab simulation. The overall goal is to help organizations develop the habits of continuous improvement, problem solving, and adaptation that underlie Toyota's success.

Scrum and Kanban - Getting the Most from Each

Michael Sahota

Scrum is the most popular Agile methodology with Kanban a growing second choice. Learn about the core parts of each one as well as how they differ so that you can find the best fit for your team or organizational context. For example, Scrum is great when you want to shake up the status quo and transform the way you work. Kanban is great when small changes are a better fit for the environment. Learn how they work and how you can use them in your environment.

Hoshin Kanri Infographics

Grant Crow

This collection of infographics focuses around Hoshin Kanri as a strategy execution methodology. The infographics presented cover the 6 steps in the Hoshin process, the Hoshin catchball process, the process of agreeing breakthrough objectives as well as the role of leading and lagging indicators in hoshin execution. Any viewer is welcome to use the embed code provided to copy and use the infographics.

Agile Software Development, Overview

Bayard Randel

This document provides an overview of agile software development. It begins by outlining the principles of the Manifesto for Agile Development, which values individuals, interactions, working software, and customer collaboration over processes, tools, documentation, and contract negotiation. The document then contrasts the traditional waterfall model with the iterative agile model. It notes several problems with waterfall such as difficulty adapting to change and long waits for value. Benefits of the agile model are then outlined, including increased productivity, reduced risk, higher customer satisfaction, and improved code quality. Case studies from a survey and Yahoo highlight positive results from adopting agile such as increased productivity and team morale.

Connecting Kata with Hoshin Kanri and True North

W3 Group Canada Inc.

Lean Management Kata Training

Carlos Martin Maroto

A Practical Approach to Strategy Deployment

Gerardo Aulinger

This document provides a simplified example of strategy deployment using a gearbox manufacturing value stream. It introduces the main players involved, including the company president, value stream leader, process owner, and frontline workers. The example illustrates how the practice of daily coaching and improvement kata can be used at different levels to work towards a target condition according to the Improvement Data way of working.

Hoshin Kanri Strategic Planning

avscully

The document discusses Hoshin Kanri, a strategic planning process that involves: 1) Conducting an environmental scan to identify business objectives and targets for key performance indicators. 2) Developing a comprehensive list of projects to meet the objectives and targets, then evaluating projects to create a priority portfolio. 3) Implementing the project portfolio through a review process involving "Project 2x2" reports, and reflecting on results to improve processes and tools for achieving targets.

Standard Work in Lean Sales and Marketing

Business901

Toyota kata and beyond

William Judd

Lean A3 for SALES EDCA/PDCA/SDCA

Business901

Plan do-check-act

Shradha Khandelwal

The document discusses the Plan-Do-Check-Act (PDCA) cycle. It explains that PDCA was popularized by Dr. Edwards Deming and is based on the scientific method of hypothesis-experiment-evaluation. The PDCA cycle involves planning a change, implementing it, observing the results, and acting on what is learned. Repeating the cycle can lead to continuous improvement. The document then outlines the four steps of PDCA - plan, do, check, act - and describes what each step entails.

Overview of SDLC - Waterfall, Agile, and more

Steve Gladstone

Continuous improvement & pdca

Shoilen Sannamat

Viewers also liked (20)

Beyond Kanban: Lean Thinking for Agile Teams

Masaaki imai and total quality management

Agile Software Development Overview

Hoshin kanri and the x matrix small

Manufacturing wastes

Identifying Waste

Improvement Kata Workshop

Scrum and Kanban - Getting the Most from Each

Hoshin Kanri Infographics

Agile Software Development, Overview

Connecting Kata with Hoshin Kanri and True North

Lean Management Kata Training

A Practical Approach to Strategy Deployment

Hoshin Kanri Strategic Planning

Standard Work in Lean Sales and Marketing

Toyota kata and beyond

Lean A3 for SALES EDCA/PDCA/SDCA

Plan do-check-act

Overview of SDLC - Waterfall, Agile, and more

Continuous improvement & pdca

Similar to Lean and Kanban Principles for Software Developers

Best practices of project management for small teams

Cake YOSHIDA

This document outlines best practices for project management in small teams using automated testing and code reviews. It recommends: 1. Requiring automated testing of all code changes. 2. Conducting code reviews between developers by creating merge requests in GitLab or GitHub. Developers make changes on branches, create merge requests, and code is automatically tested. If tests pass, another developer reviews the code and merges or provides feedback. This process improves code quality, reduces bugs, and allows for knowledge sharing between team members.

Team Development and Release Management

Salesforce Partners

If you are building a commercial Force.com app with a team of developers, this session is for you. Join us to learn best practices for setting up your Force.com IDE, managing source code, creating automated builds, deploying to test environments, and more. Hear from a panel of seasoned ISVs who are employing key team development principles. This session is primarily for product managers, architects, and developers (isvpartners).

How to Introduce Continuous Delivery

Dr. Alexander Schwartz

This document discusses introducing continuous delivery practices at an organization. It provides four stories from different companies about their continuous delivery journeys. The first story describes challenges at Nokia with complicated dependencies and integration problems that were addressed by implementing delivery pipelines and consumer driven contracts. The second story focuses on delivering value and achieving a higher release frequency, shorter cycle times, and higher release success rates at another unnamed company. The third story discusses the architecture at eBay and improvements achieved by moving to more modular code and weekly releases. The final story cautions against skipping testing phases when moving to continuous delivery. Common themes that helped organizations were taking baby steps, establishing cross-functional teams, test automation, and focusing on delivering value.

Tester developer interaction

gaoliang641

This document discusses the relationship between testers and developers and how to improve interaction between the two roles. It notes that while they sometimes have a "love-hate" relationship as they have different expertise and goals, they ultimately depend on each other to ensure high quality software. The document provides tips for when testers and developers should interact, such as during design, test case reviews, and bug fixing. It also recommends ways to build trust between testers and developers through clear communication and establishing processes for quality control.

Agile Software Development in Practice - A Developer Perspective

Wee Witthawaskul

10x Test Coverage, Less Drama: Shift Left Functional & Performance Testing

Sauce Labs

Shifting left means starting testing earlier in the development cycle by writing tests alongside code development within small teams. This eliminates surprises from late-discovered problems and ensures code meets expectations before being declared "done". To achieve superior test coverage, teams must test more by shifting left and testing as code is committed so developers get immediate feedback and bugs are fixed early. Shifting left embeds quality into every step of development and allows for continuous testing and integration to produce higher quality, shippable features faster.

Getting started with Agile

kutuma

The document provides an overview of Agile methodology and SCRUM framework. It discusses key aspects of SCRUM such as product backlog, sprint backlog, daily stand-ups, and burndown charts. It also covers Agile concepts like cross-functional teams, iterative development, and responding to change. The document aims to introduce readers to the basic principles and practices of Agile software development using SCRUM.

What CS Class Didn't Teach About Testing

Camille Bell

Software Testing with Agile Requirements Practices

A B M Moniruzzaman

The document discusses software testing practices in agile development. It covers the technical and organizational challenges of testing in an agile environment where requirements are changing frequently. It emphasizes the need to test early and often through automation, and describes strategies like test-driven development and maintaining different levels of testing at the iteration and release levels to effectively test in short iterations with changing requirements.

Zararfa SummerCamp 2012 - Community update and Zarafa Development Process

Zarafa

Zarafa focuses on community feedback to guide its development goals and priorities. It coordinates with communities through forums, wikis, projects sites, and issue trackers like JIRA. Zarafa listens to community input through various channels and has taken steps like opening its code repositories to enable direct contributions. It works to stabilize releases and support many distributions through a development process involving sprints, releases from branches, and beta testing. Contributions have the highest chance of acceptance if they address existing issues through the proper channels.

Agile2012 soccer witha_basketballteam

drewz lin

Tobias Leisgang presented at Agile 2012 on applying agile principles to integrated circuit development. Some key points: 1) Agile development approaches promote close, frequent collaboration between business and technical teams to deliver working software in short iterations, from a few weeks to a few months. 2) An analogy was drawn between agile software development and a soccer team, where a project is broken into short "steps" or sprints and flexibility and adaptation are valued over rigid plans. 3) Applying agile principles like iterative development, adaptive planning, frequent working software delivery, and collaborative self-organizing teams can help effectively manage uncertainty in integrated circuit development projects.

Continuous delivery chernivcy

Volodymyr Yelchev

The document discusses strategies for continuous delivery through parallel development and continuous integration, including maintaining feature branches, release branches, and a main development branch. It also outlines the general development workflow and processes for building, deploying, acceptance testing, releasing, and pushing updates to production through automated deployment. The goal is to enable one-click software updates and releases at any time through establishing testing, integration, and deployment best practices.

Feedback Loops

cowboyd

The document discusses building user interfaces with feedback loops. It advocates for short release cycles of 3 weeks to incorporate feedback from users and other stakeholders. This allows products to evolve based on continual feedback rather than long development cycles. Feedback loops at all levels are emphasized, including from users, developers through unit testing, and the whole team through bi-weekly demos. Embracing negative feedback and failures is presented as valuable for improving the product and experience.

TDD refresher

Kerry Buckley

The document discusses test-driven development (TDD) and provides guidance on how to implement TDD. It outlines the progression from manual testing to automated testing to test-first development. The benefits of TDD include less manual testing, faster feedback, safer code changes, and improved design. Good tests express intent, isolate areas under test, and provide clear failures. When starting TDD, automate tests for important features and bug-prone areas first, and use TDD for new features.

Understand release engineering

gaoliang641

Software Testing Life Cycle

gueste730d5

This document provides an overview of software testing fundamentals and the software development lifecycle. It discusses different types of testing including static testing, dynamic testing, component testing, integration testing, and system testing. It also addresses test planning, management, and tools. The document emphasizes that early test design helps build quality and prevents faults by finding issues early when they are cheaper to fix. An experience report shows how early testing led to fewer faults and happier users compared to a previous phase without early testing.

Creating truly player-centric games - how we do it at Kolibri Games?

GameCamp

Ntd2015_pt_kanban_ppt

Jokin Aspiazu

The document describes how PeerTransfer changed their development process from Scrum to Kanban. Some key issues with Scrum included developers having to switch contexts weekly and too many bugs to test within a sprint. With Kanban, work is pulled in a continuous flow through stages like development, code review, testing, and deployment. Kanban also uses work-in-progress limits to prevent bottlenecks and encourage pairing, and estimates to add planning structure while focusing in sprints. The team aims for quality with practices like test automation, feature reviews, and pair programming.

Agile Software Development Process Practice in Thai Culture

Wee Witthawaskul

DevOps Tutorial For Beginners | DevOps Tutorial | DevOps Tools | DevOps Train...

Simplilearn

This presentation about DevOps will help you understand what is DevOps, how is DevOps different from traditional IT, benefits of DevOps, the lifecycle of DevOps and tools used in DevOps processes. DevOps is one of the most trending IT jobs. It is a collaboration between development and operation teams which enables continuous delivery of applications and services to our end users. However, if you want to become a DevOps engineer, you must have knowledge of various DevOps tools (like Git, Maven, Selenium, Jenkins, Docker, Ansible, Nagios etc.) to achieve automation at each stage which helps in gaining Continuous Development, Continuous Integration, Continuous Testing and Continuous Monitoring in order to deliver a quality product to the client at a very fast pace. Now, let us get started and understand DevOps and does the various DevOps tools work. Below are the topics explained in this DevOps presentation: 1. What is DevOps? 2. Benefits of DevOps 3. Lifecycle of DevOps 4. Tools in DevOps Why learn DevOps? Simplilearn’s DevOps training course is designed to help you become a DevOps practitioner and apply the latest in DevOps methodology to automate your software development lifecycle right out of the class. You will master configuration management; continuous integration deployment, delivery, and monitoring using DevOps tools such as Git, Docker, Jenkins, Puppet, and Nagios in a practical, hands-on and interactive approach. The DevOps training course focuses heavily on the use of Docker containers, a technology that is revolutionizing the way apps are deployed in the cloud today and is a critical skillset to master in the cloud age. After completing the DevOps training course you will achieve hands-on expertise in various aspects of the DevOps delivery model. The practical learning outcomes of this Devops training course are: An understanding of DevOps and the modern DevOps toolsets The ability to automate all aspects of a modern code delivery and deployment pipeline using: 1. Source code management tools 2. Build tools 3. Test automation tools 4. Containerization through Docker 5. Configuration management tools 6. Monitoring tools Who should take this course? DevOps career opportunities are thriving worldwide. DevOps was featured as one of the 11 best jobs in America for 2017, according to CBS News, and data from Payscale.com shows that DevOps Managers earn as much as $122,234 per year, with DevOps engineers making as much as $151,461. DevOps jobs are the third-highest tech role ranked by employer demand on Indeed.com but have the second-highest talent deficit. 1. This DevOps training course will be of benefit the following professional roles: 2. Software Developers 3. Technical Project Managers 4. Architects 5. Operations Support 6. Deployment engineers 7. IT managers 8. Development managers Learn more at https://www.simplilearn.com/cloud-computing/devops-practitioner-certification-training

Similar to Lean and Kanban Principles for Software Developers (20)

Best practices of project management for small teams

Team Development and Release Management

How to Introduce Continuous Delivery

Tester developer interaction

Agile Software Development in Practice - A Developer Perspective

10x Test Coverage, Less Drama: Shift Left Functional & Performance Testing

Getting started with Agile

What CS Class Didn't Teach About Testing

Software Testing with Agile Requirements Practices

Zararfa SummerCamp 2012 - Community update and Zarafa Development Process

Agile2012 soccer witha_basketballteam

Continuous delivery chernivcy

Feedback Loops

TDD refresher

Understand release engineering

Software Testing Life Cycle

Creating truly player-centric games - how we do it at Kolibri Games?

Ntd2015_pt_kanban_ppt

Agile Software Development Process Practice in Thai Culture

DevOps Tutorial For Beginners | DevOps Tutorial | DevOps Tools | DevOps Train...

More from Cory Foy

Defending Commoditization: Mapping Gameplays and Strategies to Stay Ahead in ...

Lean and Kanban Principles for Software Developers

Recommended

Recommended

More Related Content

What's hot

What's hot (17)

Viewers also liked

Viewers also liked (20)

Similar to Lean and Kanban Principles for Software Developers

Similar to Lean and Kanban Principles for Software Developers (20)

More from Cory Foy

More from Cory Foy (20)

Recently uploaded

Recently uploaded (20)

Lean and Kanban Principles for Software Developers

Editor's Notes