Agile and lean methods for managing application development process
|
|
- Jeremy Sullivan
- 5 years ago
- Views:
Transcription
1 Agile and lean methods for managing application development process Hannu Markkanen
2 Lifecycle model To support the planning and management of activities required in the production of e.g. goods, software, or information systems, various lifecycle models have been developed A lifecycle model establish the order in which a project specifies, prototypes, designs, implements, reviews, tests, i.e. performs its activities. Waterfall Code-and-Fix Prototyping 2
3 Generic Project Life Cycle Phase Defining (or Scoping) Planning Executing Monitoring/Controlling Closing Tasks Defining the high-level objectives and requirements of the project What, who, when? With what resources? Organising people Allocating resources Scheduling the work Tracking of progress Taking corrective actions Reflecting and improving continuously (lean) Evaluation of what was done Information for later projects 3
4 Waterfall model Strenghts The waterfall model performs well for projects in which you have a stable product definition Do such projects exist? Weaknesses The waterfall model is inflexible. Is it possible to specify the requirements at the beginning of the project? Is it possible to design and implement all parts of the application at the same pace? 4
5 Code-and-Fix Strenghts No planning and design overhead, time is spend on pure coding Requires no process management experience. Weaknesses Useful only for tiny applications. In case of real life projects, dangerous! 5
6 Prototyping Develop a prototype, show it to your customer, and refine it based on the feedback Strenghts Flexibility (with changing requirements) Reduced time and cost Weaknesses Can distract developers from properly analyzing the complete project Can easily result in the code-and-fix development. Good for applications with lots of user interaction Most Agile Methods rely heavily upon prototyping techniques. 6
7 Overview of lean and agile software development
8 Lean software development Lean software development is an adaptation of Lean manufacturing principles and practices Based on the Toyota Production System The core lean principles: Eliminate waste Extra features (unnecessary functionality) Partially done work Task switching Delays (waiting for work) Bureaucracy Defects Focus on learning and improvement Build quality in the process Decide as late as possible Deliver as fast as possible (customer value) Empower the team 8
9 Two Axioms of Lean Software Engineering (David Joyce) 1. It is possible to divide the work into small value adding increments, that can be independently scheduled 2. It is possible to develop any value adding increment in a continuous flow, from requirement to deployment 9
10 Dividing the work to small increments 10
11 Dividing the work to small increments Time on the job Client Time of getting the first batch Time of whole production 11
12 Agile software development A group of software development methodologies based on iterative and incremental development Requirements and solutions evolve through collaboration between self-organized cross-functional teams Agile Manifesto - values: 1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a detailed plan Popular Agile methods Extreme Programming (XP) Scrum 12
13 Agile practices User stories Regular meetings Planning meeting Daily Stand-up meeting Retrospective meeting Refactoring of code Continuous integration 13
14 Scrum overview Short, time-boxed iterations 14
15 Kanban
16 Background of Kanban Kanban is a Japanese word that literally means signal card In a manufacturing environment, this card is used as a signal to tell an upstream stage in a process to produce more Kanban is a pull system New work is pulled into a stage in the system when there is capacity to handle it, rather than being pushed based on demand The workers at each stage in the process are not allowed to do work unless they are signaled from a downstream stage A pull system cannot be overloaded if the capacity of each step has been set appropriately The first kanban system for software engineering was implemented at Microsoft beginning in
17 Kanban as an Adaptive System to achieve Lean The Kanban Method is an adaptive system for catalyzing Lean behaviour (complex, adaptive, emergent behavior) Kanban core concepts Visualize workflow Limit Work-in-Process Help work to flow Kanban is not a software development methodology Does not provide methods for any particular development task, like testing or requirements Teams adopt practices e.g. from agile methods (such as pair programming in XP) 17
18 Implementing Kanban
19 Work Item Types Identify the types of work that will need to be limited. Typical work item types: Incoming work E.g. User Story, Use Case, functional requirement, feature, The incoming work type might be hierarchical, such as Epic, a collection of user stories. Bug Change Request Maintenance Refactoring Improvement Suggestion Infrastucture update Blocking Issue 19
20 Kanban workflow There is a queue of work, which goes through a number of stages until its done When work is completed in a stage, it is pulled downstream for the next stage 20
21 Kanban board Vertical columns for stages (phases) in the workflow, i.e. activities through which the work progresses Input queue ( Backlog ) Done stage ( RTS ) Work-In-Process (WIP) limits The max number of work items that can be in a stage at any moment Typically, the work-in-process limits are drawn on the board at the top of each column (or across a span of columns) Pull is signaled if the number of cards in a column is less than the indicated limit Why WIP is important? To deliver new value quickly, limit the amount of work done at one time Context switching costs 20% productivity 21
22 Setting the WIP limits WIP limits for work tasks should be set as an average number of items per person, developer pair, or small, collaborative team Typically, the limit should be in the range of one to three items per person, pair, or team Do not waste time in trying to determine the perfect WIP limit; simply pick a number based on best guess, and make progress Adjust the WIP limit empirically if necessary There is no magic formula for your choice. You can select a number and then observe whether it is working well. If not, adjust it up or down 22
23 It s a Mistake Not to Set a WIP Limit The tension created by imposing a WIP limit across the value-stream is positive tension This positive tension forces discussion about the organization s issues and dysfunctions The dysfunctions generate impediments to flow and result in sub-optimal productivity and quality The discussion and collaboration invoked by the positive tension of a WIP limit is the mechanism that enables the emergence of a continuous-improvement culture 23
24 Kanban card conventions Use text or color to communicate the work item type Write other necessary information on the card as well, e.g. assigned staff member start date electronic tracking number, status information (such as whether the item is late) 24
25 Kanban board examples 25
26 Kanban board with swim lane for urgent work 26
27 Electronic Kanban board For teams that are distributed geographically, or with members working from home In your project, use one of these free tools: (or 2.0 beta at: 27
28 Coordination within Kanban Issue management, escalation, and resolution is a core discipline in improving the performance of a team and should be addressed early in the development of the team Daily standup meetings should be used to discuss issues, impediments, and flow Holding regular meetings reduces the coordination cost for those meetings and improves attendance Daily standups are an essential part of the culture of continuous improvement Provide an opportunity for all stakeholders to suggest and discuss improvement opportunities The period immediately after the standup often develops into an informal process improvement discussion (After meeting) 28
29 Daily Standup Meetings The Kanban board contains all the information about who is working on what The project manager will walk the board The convention has developed to work backward from right to left (in the direction of pull) through the tickets on the board. The facilitator might solicit a status update on a ticket or simply ask if there is any additional information that is not on the board and may not be known to the team We will practise these during the project class sessions on Thu/Fri 29
30 The After Meeting The After Meeting consists of small groups of 2 or 3 people meeting after the standup To discuss something specific topics perhaps a blocking issue, perhaps a technical design or architecture issue, but more often, a process-related issue After Meetings generate improvement ideas and result in process tailoring and innovation The After Meeting is a vital element of the cultural transformation that emerges with Kanban We will have these during the class sessions with any group who indicated need in the standup meeting 30
31 Queue Replenishment Meetings Purpose is to fill the kanban system input queue ( ToDo ) for the project Features, user stories/epics etc. from the backlog (if in use) Prioritization of new work into the input queue for development At regular intervals Prioritization of new work involves coordination of many people from various functions Group of business representatives or product owners All interested members of the development team should be present 31
32 Retrospective meeting The whole team analyzes their own process At regular intervals 32
33 Issues = blocked work items A first-class work item type used to track problems causing other work to block. Usually indicated by a bright colour The issue will remain open until the impediment is removed and the original work item can progress through the system Issue management should be a strong focus of daily standup meetings 33
34 Writing user stories
35 Writing a user story Template: As a <some role>, I want <something>, [so that <some value>] Describe who wants, what wants [and what for] in one sentence. Do not define any details of the implementation in the user story. Examples: As an end user I want to be able to upload my picture to my profile page, so that people can easily identify me As a sales person, I want to see statistics of my performance in graphical charts, so that I monitor my performance As an administrator, I want to have database backups, so that I won t be in big trouble if something unexpected happens 35
36 Writing a user story Example of breaking down a story into smaller stories: Example of breaking down a story into tasks: Henrik Kniberg: Scrum and XP from the Trenches 36
37 Defining tasks Size of the tasks Practices vary, typically from one to few days of work Split too large tasks into smaller ones Writing too small tasks is a waste (defining takes more time than doing the tasks) Issues and critical tasks can be put on the board even if they are tiny not to forget Sizing is based on experience Write clear task descriptions Every team member must understand what will be done in the task Every team member can/should write tasks Team members pick the tasks, they are not assigned (e.g. by the project manager) 37
Agile and lean methods for managing application development process
Agile and lean methods for managing application development process Hannu Markkanen 24.01.2013 1 Application development lifecycle model To support the planning and management of activities required in
Lean Software Development and Kanban
1 of 7 10.04.2013 21:30 Lean Software Development and Kanban Learning Objectives After completing this topic, you should be able to recognize the seven principles of lean software development identify
Kanban For Software Engineering
Kanban For Software Engineering Jaco van der Merwe Electromagnetic Software & Systems (EMSS) 18/8/2010 jvdmerwe@emss.co.za FEKO 1 General Applications of FEKO Antennas Antenna placement Microwave components
What is meant by the term, Lean Software Development? November 2014
What is meant by the term, Lean Software Development? Scope of this Report November 2014 This report provides a definition of Lean Software Development and explains some key characteristics. It explores
The Agile Manifesto is based on 12 principles:
The Agile Manifesto is based on 12 principles: Customer satisfaction by rapid delivery of a useful product solution Welcome changing requirements, even late in development Working products are delivered
Scrum vs. Kanban vs. Scrumban
Scrum vs. Kanban vs. Scrumban Prelude As Agile methodologies are becoming more popular, more companies try to adapt them. The most popular of them are Scrum and Kanban while Scrumban is mixed guideline
Introduction to Agile and Scrum
Introduction to Agile and Scrum Matthew Renze @matthewrenze COMS 309 - Software Development Practices Purpose Intro to Agile and Scrum Prepare you for the industry Questions and answers Overview Intro
Agile support with Kanban some tips and tricks By Tomas Björkholm
Agile support with Kanban some tips and tricks By Tomas Björkholm Foreword A year ago I held an Open Space at Scrum Gathering in Stockholm about Agile Support. I have since received several requests to
LEAN AGILE POCKET GUIDE
SATORI CONSULTING LEAN AGILE POCKET GUIDE Software Product Development Methodology Reference Guide PURPOSE This pocket guide serves as a reference to a family of lean agile software development methodologies
MTAT.03.094 Software Engineering
MTAT.03.094 Software Engineering Lecture 12: Lean & Flow-based (KANBAN) Principles and Processe Fall 2015 Dietmar Pfahl email: dietmar.pfahl@ut.ee Structure of Lecture 12 KANBAN Case Study: Scrum vs. KANBAN
SESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization
SESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization Secrets of a Scrum Master: Agile Practices for the Service Desk Donna Knapp Curriculum Development Manager, ITSM Academy
Kanban vs Scrum Making the most of both
Kanban vs Scrum Making the most of both JAOO, Aarhus Oct 6, 2009 Henrik Kniberg Agile/Lean coach @ Crisp, Stockholm Board of directors henrik.kniberg@crisp.se +46 70 4925284 Purpose of this presentation
agenda AGILE AT SCALE
Copyright Net Objectives, Inc. All Rights Reserved 1 AGILE AT SCALE 1. THE CHALLENGE HIERARCHY VS. WORKFLOW 2. VALUE STREAM IMPEDANCE 3. ALLOCATE PEOPLE TO MOST VALUABLE WORK 4. MANAGING FLOW ACROSS ENTIRE
Agile Projects 7. Agile Project Management 21
Contents Contents 1 2 3 Agile Projects 7 Introduction 8 About the Book 9 The Problems 10 The Agile Manifesto 12 Agile Approach 14 The Benefits 16 Project Components 18 Summary 20 Agile Project Management
Agile Development Overview
Presented by Jennifer Bleen, PMP Project Services Practice of Cardinal Solutions Group, Inc. Contact: Agile Manifesto We are uncovering better ways of developing software by doing it and helping others
AGILE - QUICK GUIDE AGILE - PRIMER
AGILE - QUICK GUIDE http://www.tutorialspoint.com/agile/agile_quick_guide.htm Copyright tutorialspoint.com AGILE - PRIMER Agile is a software development methodology to build a software incrementally using
Kanban. Marek Majchrzak, Andrzej Bednarz Wrocław, 07.06.2011
Kanban Marek Majchrzak, Andrzej Bednarz Wrocław, 07.06.2011 Why Kanban? Jim: Now we ve finally gone all-out Scrum! Fred: So how s it going? Jim: Well, it s a lot better than what we had before... Fred:...but?
Kanban. A Toyota s manufacturing system for Software Development CERN EUROPEAN ORGANIZATION FOR NUCLEAR RESEARCH. Eloy Reguero Fuentes
CERN Kanban A Toyota s manufacturing system for Software Development Who am I? Eloy Reguero Fuentes (Noreña - Spain) Computer Science Engineer (Universidad de Oviedo 2007) SoKware Engineer at CERN (2007)
Software Engineering I (02161)
Software Engineering I (02161) Week 8 Assoc. Prof. Hubert Baumeister DTU Compute Technical University of Denmark Spring 2015 Last Week State machines Layered Architecture: GUI Layered Architecture: Persistency
SECC Agile Foundation Certificate Examination Handbook
Versions 2.0 Version Date Remarks 1.0 12/4/2012 Initial version 2.0 3/8/2008 REVISION HISTORY Updated knowledge areas Added questions examples Updated suggested readings section Page 2 of 15 Version 2.0
Lean QA: The Agile Way. Chris Lawson, Quality Manager
Lean QA: The Agile Way Chris Lawson, Quality Manager The Quality Problem Agile Overview Manifesto Development Methodologies Process Agile QA Lean QA Principles An Agile QA Framework Summary Q & A Agenda
Getting Started with Agile Project Management Methods for Elearning
Getting Started with Agile Project Management Methods for Elearning Megan Torrance TorranceLearning Training2013 Session 108 February 18, 2013 8am Megan Torrance has 20 years of experience in the learning
Agile Requirements Definition and Management (RDM) How Agile requirements help drive better results
Thought Leadership: Requirements Definition and Management Agile Requirements Definition and Management (RDM) How Agile requirements help drive better results Jason Moccia One of the myths of Agile software
Secrets of a Scrum Master: Agile Practices for the Service Desk
Secrets of a Scrum Master: Agile Practices for the Service Desk #askitsm @ITSMAcademy @ITSM_Lisa @ITSM_Donna ITSM Academy About ITSM Academy NextGen ITSM Education: Certified Process Design Engineer (CPDE)
Lean Metrics How to measure and improve the flow of work. Chris Hefley, CEO of LeanKit. November 5 th, 2014
Lean Metrics How to measure and improve the flow of work Chris Hefley, CEO of LeanKit November 5 th, 2014 Introduction to Lean Metrics What metrics should you measure? How to track them? What effect do
Real Life Risk Based Project Management for LEAN and Agile Development
Real Life Risk Based Project Management for LEAN and Agile Development D Clark, J Krumm, S Moen, K Snodgrass, A Morris U.S. Department of Transportation John A. Volpe National Transportation Systems Center
Scrum and Kanban 101
Scrum and Kanban 101 www.bebetterleader.com @jfiodorova What are your expectations What are the differences between Agile and Traditional? What do you know about Agile Two approaches to control any process:
D25-2. Agile and Scrum Introduction
D25-2 Agile and Scrum Introduction How to Use this Download This download is an overview of a discussion Intertech has with clients on Agile/Scrum This download has an overview of Agile, an overview of
Introduction to Agile Scrum
Introduction to Agile Scrum by Julia M. Lobur Penn State Harrisburg CMPSC 487W Fall 2015 Introduction to Scrum Learning Goals Relationship of Scrum to other Agile methods Scrum Framework Scrum Roles Scrum
Agile Notetaker & Scrum Reference. Designed by Axosoft, the creators of OnTime the #1 selling scrum software.
Agile Notetaker & Scrum Reference Designed by Axosoft, the creators of OnTime the #1 selling scrum software. Scrum Diagram: Team Roles: roduct Owner: Is responsible for what goes into the product backlog
Executive Guide to SAFe 24 July 2014. An Executive s Guide to the Scaled Agile Framework. alshall@netobjectives.com @AlShalloway
An Executive s Guide to the Scaled Agile Framework Al Shalloway CEO, Net Objectives Al Shalloway CEO, Founder alshall@netobjectives.com @AlShalloway co-founder of Lean-Systems Society co-founder Lean-Kanban
Introduction. Industries across the globe are burgeoning. Stiff
Solutions for higher performance! Agile VS Lean THE COMPREHENSIVE FACTORS Introduction Introduction Industries across the globe are burgeoning. Stiff competition has permeated every stratum among enterprises.
Agile Software Development. Stefan Balbo / Patrick Dolemieux
Agile Software Development Stefan Balbo / Patrick Dolemieux Agile Software Development Stefan Balbo / Patrick Dolemieux Content Why go Agile? Introduction to Scrum - Process - Roles Agile Estimating and
Kanban vs Scrum Making the most of both
Kanban vs Scrum Making the most of both QCon, San Francisco Nov 18, 2009 Henrik Kniberg Agile/Lean coach @ Crisp, Stockholm http://www.crisp.se/henrik.kniberg Background: developer, manager, entreprenuer
Agile Beyond The Team 1
Agile Beyond The Team 1 Dilbert Agile 2 What Does Your Organization Value? Projects over Teams? Do new teams spools up for new projects? On-Time/On-Budget Delivery over Zero Maintenance Products Deliver
Kanban A Lean approach to Agile software development
Kanban A Lean approach to Agile software development JFokus January 26, 2010 Henrik Kniberg Agile/Lean coach www.crisp.se Board of directors henrik.kniberg@crisp.se 070 4925284 Goals of this tutorial Basic
Capstone Agile Model (CAM)
Capstone Agile Model (CAM) Capstone Agile Model (CAM) Approach Everything we do within the Capstone Agile Model promotes a disciplined project leadership process that encourages frequent inspection and
Program & Portfolio! Management using! Kanban! Copyright 2013 Davisbase Consulting. Limited Display License Provided to ASPE
Program & Portfolio! Management using! Kanban! Introduction and Agenda Tom Wessel, Davisbase Consulting 20 years in software development. Over 7 years working with software development teams, training,
Waterfall to Agile. DFI Case Study By Nick Van, PMP
Waterfall to Agile DFI Case Study By Nick Van, PMP DFI Case Study Waterfall Agile DFI and Waterfall Choosing Agile Managing Change Lessons Learned, Sprints Summary Q and A Waterfall Waterfall Waterfall
Life Cycle Models. V. Paúl Pauca. CSC 331-631 Fall 2013. Department of Computer Science Wake Forest University. Object Oriented Software Engineering
Life Cycle Models V. Paúl Pauca Department of Computer Science Wake Forest University CSC 331-631 Fall 2013 Software Life Cycle The overall framework in which software is conceived, developed, and maintained.
www.stephenbarkar.se Lean vs. Agile similarities and differences 2014-08-29 Created by Stephen Barkar - www.stephenbarkar.se
1 www.stephenbarkar.se Lean vs. Agile similarities and differences 2014-08-29 Purpose with the material 2 This material describes the basics of Agile and Lean and the similarities and differences between
How To Plan An Agile Project
GAO Scheduling Best Practices Applied to an Agile Setting by Juana Collymore and Brian Bothwell April 15, 2015 Outline Why is scheduling important? GAO Schedule Assessment Guide Overview Status of the
Taking the first step to agile digital services
Taking the first step to agile digital services Digital Delivered. Now for Tomorrow. 0207 602 6000 mbailey@caci.co.uk @CACI_Cloud 2 1. Background & Summary The Government s Digital by Default agenda has
Kanban kick- start. By Tomas Björkholm at Crisp, April 2011
Kanban kick- start By Tomas Björkholm at Crisp, April 2011 INTRODUCTION... 1 AN APPROACH TO GET STARTED WITH KANBAN... 2 STEP 1 GET TO KNOW YOUR SYSTEM... 2 STEP 2 IDENTIFY YOUR SOURCES AND PRIORITIZE...
Lean and Agile Development With Scrum (Part 2) Lucio Davide Spano
Lean and Agile Development With Scrum (Part 2) Lucio Davide Spano lucio.davide.spano@isti.cnr.it spano@di.unipi.it 7 May 2012 Dilbert intro Summary Sprint Review Done at the end of the Sprint Not a simple
Today: Software Development Models (cont)
Today: Software Development Models (cont) CPSC 491 Development Processes (aka Development Lifecycle) Define the steps, and their order, to be carried out The main steps (or phases) generally include: 1.
Role of the Business Analyst in an Agile Project
Role of the Business Analyst in an Agile Project Agenda 1: Introduction to Agile 2: Focus on Agile Principles 3: Business Analysis and the agile process 4: Addressing challenges 5: Close off and recap
The style is: a statement or question followed by four options. In each case only one option is correct.
AGILE FOUNDATION CERTIFICATE SAMPLE FOUNDATION QUESTIONS WITH ANSWERS This document is a set of sample questions, in the style of the Agile Foundation Certificate Examination, which is a 60 question, 1
Applying Lean on Agile Scrum Development Methodology
ISSN:2320-0790 Applying Lean on Agile Scrum Development Methodology SurendRaj Dharmapal, Dr. K. Thirunadana Sikamani Department of Computer Science, St. Peter University St. Peter s College of Engineering
Software Engineering Process Economy & Quality
Project delivery: Progress report Software Engineering Process Economy & Quality ETSF 01 http://cs.lth.se/etsf01 The SPA reports you RECEIVED Your actions on received feedback Excel format preferred Lecture
Introduction to Agile Software Development Process. Software Development Life Cycles
Introduction to Agile Software Development Process Presenter: Soontarin W. (Senior Software Process Specialist) Date: 24 November 2010 AGENDA Software Development Life Cycles Waterfall Model Iterative
10/4/2013. Sharif University of Technology. Session # 3. Contents. Systems Analysis and Design
Session # 3 Contents Systems Analysis and Design 2 1 Tiers of Software Development 10/4/2013 Information system development project Realistic behavior 3 Information system development project System Development
Kanban what is it and why should I care?
Kanban what is it and why should I care? Abstract Landon Reese Kathy Iberle Kanban is gaining popularity in the software development world. It deserves to be considered as a means to manage software development.
www.testing-solutions.com TSG Quick Reference Guide to Agile Development & Testing Enabling Successful Business Outcomes
www. TSG Quick Reference Guide to Agile Development & Testing Enabling Successful Business Outcomes What is Agile Development? There are various opinions on what defines agile development, but most would
AGILE & SCRUM. Revised 9/29/2015
AGILE & SCRUM Revised 9/29/2015 This Page Intentionally Left Blank Table of Contents Scrum Fundamentals Certified Course... 1 Scrum Developer Certified (SDC)... 2 Scrum Master Certified (SMC)... 3 Scrum
XP 2015 Presenter-Nirnaya Tripathi Date 27.05.2015
Scaling Kanban for software development in a multisite organization: Challenges and Potential Solution Nirnaya Tripathi, Pilar Rodríguez, Muhammad Ovais Ahmad, Markku Oivo XP 2015 Presenter-Nirnaya Tripathi
Course Title: Managing the Agile Product Development Life Cycle
Course Title: Managing the Agile Product Development Life Cycle Course ID: BA25 Credits: 28 PDUs Course Duration: 4 days (with optional Executive session) Course Level: Intermediate/Advanced Course Description:
SCALING AGILE. minutes
SCALING AGILE in 5 minutes THREE AGILE COMPANIES Basement Apps Ltd is having unexpected success with a social media app for musicians. Software Supply Ltd needs more diverse development teams as the company
USCIS/SPAS: Product Backlog Items and User Stories 4/16/2015. Dr. Patrick McConnell
USCIS/SPAS: Product Backlog Items and User Stories 4/16/2015 Dr. Patrick McConnell July 9, 2015 1 First, an old joke.. I can t identify an original source for this cartoon. As best as I can tell, the art
Agile In a Nutshell. Note - all images removed to fit 2MB limit Actual presentation has much more content. Jonathan Rasmusson
Agile In a Nutshell Note - all images removed to fit 2MB limit Actual presentation has much more content Jonathan Rasmusson What we re going to cover How agile works What to expect What agile is Agile
AGILE vs. WATERFALL METHODOLOGIES
AGILE vs. WATERFALL METHODOLOGIES Introduction Agile and waterfall are two major methodologies that software developers and project managers have the option of using. Some of the goals of developers and
Scrum methodology report
Scrum methodology report Author: Tsholofelo Eunice Moitsheki Student number Tsholofelo Moitsheki (463642) Project Source and Documentation: http://kenai.com/downloads/dotsboxes/group%20report/dab5_scrum
When agile is not enough
When agile is not enough LESS 2010 Kati Vilkki kati.vilkki@nsn.com 1 Nokia Siemens Networks When agile is not enough What does lean thinking add to agile? Combining agile and lean Change in mind-set Management
Integrating PRINCE2 and Scrum for successful new product development
1 Goal Professional Services Pty Ltd 2 Renewtek Pty Ltd Integrating PRINCE2 and Scrum for successful new product development Rankins G J 1 and Kearns M 2 This paper was presented at the Australian Institute
Agile to the Bone. Introduction to Agile by Pietari Kettunen
Agile to the Bone Introduction to Agile by Pietari Kettunen Agenda Problem with traditional software engineering Why Agile is the solution? Roots of Agile Values of Agile Common implementations Scrum Kanban
Lean Agile Scrum Business Value Development and Delivery using Agility. Brenden McGlinchey Software Done Right, Inc. brenden@softwaredoneright.
Lean Agile Scrum Business Value Development and Delivery using Agility Brenden McGlinchey Software Done Right, Inc. brenden@softwaredoneright.net High yield software engineering team Active Customer Involvement
Course Title: Planning and Managing Agile Projects
Course Title: Planning and Managing Agile Projects Course ID: BA15 Credits: 21 PDUs Course Duration: 3 days (Live in person class only) Course Level: Basic/Intermediate Course Description: This 3-day course
Software Development Life Cycle (SDLC)
Software Development Life Cycle (SDLC) Supriyo Bhattacharjee MOF Capability Maturity Model (CMM) A bench-mark for measuring the maturity of an organization s software process CMM defines 5 levels of process
Gothenburg 2015 Jan Marek Jan.Marek@ca. com CA Technologies Introducing Agile development methodologies to Session S601 mainframe development teams
Jan Marek Jan.Marek@ca. com CA Technologies Session S601 Introducing Agile development methodologies to mainframe development teams Agenda Introduce Agile software development methodologies Scrum overview
Agile extreme Development & Project Management Strategy Mentored/Component-based Workshop Series
Overview This is a 15-day live facilitator-led or virtual workshop is designed to prompt your entire team to work efficiently with Microsoft s Application Lifecycle Management solution based around Visual
An Introduction to Kanban for Scrum Users. Stephen Forte Chief Strategy Officer, Telerik @worksonmypc Stevef.hk@gmail.com
An Introduction to Kanban for Scrum Users Stephen Forte Chief Strategy Officer, Telerik @worksonmypc Stevef.hk@gmail.com 1 About the Speaker Chief Strategy Officer of Telerik Board Member of the Scrum
Agile Project Management and Agile Practices Training; with a Scrum Project that you will do.
1 PMI Agile Certified Practitioner (PMI-ACP) workshop course details. We are unique and specialists in Agile! Your workshop trainer by passion and is a senior Agile Coach who coached many teams and Kanban
A Comparison between Five Models of Software Engineering
International Journal of Research in Information Technology (IJRIT) www.ijrit.com ISSN 2001-5569 A Comparison between Five Models of Software Engineering Surbhi Gupta, Vikrant Dewan CSE, Dronacharya College
Introduction to Software Kanban
Introduction to Software Kanban Darian Rashid Agile Trainer & Coach darian@agileethos.com 1 Topics Push vs. Pull Systems Introduction to Lean/Kanban Traditional Wastes in Lean Standard Development Taskboard
Agile Project Management
Agile Project Management Projekt-Kick-Off-Tage Hochschule Augsburg Martin Wagner, 15. März 2011 TNG Technology Consulting GmbH, http://www.tngtech.com Agile project management with Scrum Agenda Software
Topics covered. Agile methods Plan-driven and agile development Extreme programming Agile project management Scaling agile methods
Topics covered Chapter 3 Agile Software Development Agile methods Plan-driven and agile Extreme programming Agile project management Scaling agile methods 1 2 Need for rapid software Rapid software Changing
Lean and Kanban at Scale Extending Kanban across the portfolio, program and team levels. Al Shalloway, Net Objectives. September 4 th, 2014
Lean and Kanban at Scale Extending Kanban across the portfolio, program and team levels Al Shalloway, Net Objectives September 4 th, 2014 Implementing Kanban at Scale Al Shalloway, CEO & Founder of Net
A Viable Systems Engineering Approach. Presented by: Dick Carlson (richard.carlson2@boeing.com)
A Viable Systems Engineering Approach Presented by: Dick Carlson (richard.carlson2@boeing.com) Philip Matuzic (philip.j.matuzic@boeing.com) i i Introduction This presentation ti addresses systems engineering
From Agile by Design. Full book available for purchase here.
From Agile by Design. Full book available for purchase here. Contents Introduction xiii About the Author xix Chapter 1 Adjusting to a Customer-Centric Landscape 1 It s a Whole New World 1 From Customer-Aware
Water-Scrum-Fall Agile Reality for Large Organisations. By Manav Mehan Principal Agile consultant Manav.Mehan@tcs.com
Water-Scrum-Fall Agile Reality for Large Organisations By Manav Mehan Principal Agile consultant Manav.Mehan@tcs.com Interests and Experience Leading Change and Transformation in Large, Complex organisations
CS435: Introduction to Software Engineering! " Software Engineering: A Practitioner s Approach, 7/e " by Roger S. Pressman
CS435: Introduction to Software Engineering! " " " " " " " "Dr. M. Zhu! Chapter 3! Agile Development! Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e " by Roger S. Pressman
Improving Software Development through Combination of Scrum and Kanban
Improving Software Development through Combination of Scrum and Kanban VILJAN MAHNIC Faculty of Computer and Information Science University of Ljubljana Trzaska 25, SI-1000 Ljubljana SLOVENIA viljan.mahnic@fri.uni-lj.si
Process Methodology. Wegmans Deli Kiosk. for. Version 1.0. Prepared by DELI-cious Developers. Rochester Institute of Technology
Process Methodology for Wegmans Deli Kiosk Version 1.0 Prepared by DELI-cious Developers Rochester Institute of Technology September 15, 2013 1 Table of Contents 1. Process... 3 1.1 Choice... 3 1.2 Description...
Getting Started with Kanban Paul Klipp
Getting Started with Kanban Paul Klipp kanbanery 2 Contents 3/ Getting Started with Kanban 4/ What is Kanban? 7/ Using Kanban Does kanban apply to me? How can it help me? What will I have to change? 10/
Agile vs. Waterfall. Why not both. Arnold Okkenburg PMP
Agile vs. Waterfall Why not both Arnold Okkenburg PMP Project Management Agile Project Management Traditional Project Management Key Questions for Project Managers 1. Impact on Existing Project Methodologies:
Software Development Methodologies
Software Development Methodologies Jonathan Hoyle Eastman Kodak Thursday, June 2, 2005 Overview Predictive Methodologies Waterfall Other Predictive Methodologies Agile Methodologies Extreme Programming
Managing Agile Projects in TestTrack GUIDE
Managing Agile Projects in TestTrack GUIDE Table of Contents Introduction...1 Automatic Traceability...2 Setting Up TestTrack for Agile...6 Plan Your Folder Structure... 10 Building Your Product Backlog...
CSPO Learning Objectives Preamble. Scrum Basics
CSPO Learning Objectives Preamble This document contains topics for the Certified Scrum Product Owner (CSPO) training course. The purpose of this document is to describe the minimum set of concepts and
Preparation Guide. EXIN Agile Scrum Foundation
Preparation Guide EXIN Agile Scrum Foundation Edition March 2014 Copyright 2014 EXIN All rights reserved. No part of this publication may be published, reproduced, copied or stored in a data processing
When is Agile the Best Project Management Method? Lana Tylka
When is Agile the Best Project Management Method? Lana Tylka Staged Incremental Deliveries Prototypes Plan Develop Design Deploy Test Maintain Sequential Steps Multiple Iterations Waterfall Sprints, Spirals
Agile project management: A magic bullet?
Agile project management: A magic bullet? Prof. Darren Dalcher d.dalcher@mdx.ac.uk Conferencia Iberoamericana de Calidad del Software Prof. Darren Dalcher 1 Outline I. What is agilility? The agile manifesto
Agile Development with Rational Team Concert
AM1 Agile Development with Rational Team Concert Giles Davies Technical Consultant, IBM Rational giles.davies@uk.ibm.com What is Agile? An iterative and incremental (evolutionary) approach performed in
Global Business Services, GBS. Scrum and Kanban. Processer & IT nord seminar 5v3. Gitte Klitgaard Hansen, IBM
Scrum and Kanban Processer & IT nord seminar 5v3 Gitte Klitgaard Hansen, IBM Agenda Who am I? My background in scrum and agile Basics of scrum Basics of kanban When do you use scrum and kanban? 2 Who am
Lean. Agile. Demystifying Kanban. White Papers. essential. by Alan Shalloway. Business-Driven Software Development
Lean Agile Demystifying Kanban by Alan Shalloway essential White Papers Business-Driven Software Development Demystifying Kanban A Net Objectives Essential White Paper Net Objectives Press, a division
ASSESSMENT OF SOFTWARE PROCESS MODELS
ASSESSMENT OF SOFTWARE PROCESS MODELS Akhilesh Research Scholar, Department of Computer Science, Manav Bharti University, Solan (H.P.) ABSTRACT The field of software engineering is related to the development
Transitioning Your Software Process To Agile Jeffery Payne Chief Executive Officer Coveros, Inc. jeff.payne@coveros.com www.coveros.
Transitioning Your Software Process To Agile Jeffery Payne Chief Executive Officer Coveros, Inc. jeff.payne@coveros.com www.coveros.com 1 About Coveros Coveros helps organizations accelerate the delivery
The only person who likes change is a baby with a wet diaper. Mark Twain. Charan CA Atreya
The only person who likes change is a baby with a wet diaper. Mark Twain Charan CA Atreya November - Evolutionary adoption of agile principles in traditional organizations First introduce Kanban and get
Introduction to Agile
Chapter 1 Introduction to Agile Objectives: Define Agile software development Explain differences and similarities between various lightweight methodologies Learn the core principles of Agile Dispel common
WHY KANBAN? Troy Tuttle. blog.troytuttle.com. twitter.com/troytuttle. linkedin.com/in/troytuttle. Project Lead Consultant, AdventureTech
WHY KANBAN? 1 Troy Tuttle Project Lead Consultant, AdventureTech Troy.Tuttle@adventuretechgroup.com TroyLTuttle@gmail.com blog.troytuttle.com twitter.com/troytuttle linkedin.com/in/troytuttle Motivation
CSE 435 Software Engineering. Sept 16, 2015
CSE 435 Software Engineering Sept 16, 2015 2.1 The Meaning of Process A process: a series of steps involving activities, constraints, and resources that produce an intended output of some kind A process