Agile Samurai Principles. Agile Development Deliver Value Every Iteration Break big problems into smaller ones Focus on most important issues Deliver.

Slides:



Advertisements
Similar presentations
© Copyright 2006 FPT Software 1 © FPT SOFTWARE – TRAINING MATERIAL – Internal use 04e-BM/NS/HDCV/FSOFT v2/3 How to work in Fsoft project Authors: KienNT.
Advertisements

© 2007 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. Interactive Solutions & Design Group.
AgileMan Consulting So what the heck is Agile? It came about as a response to the high failure rate of software projects (> 60%), where failure means late,
Software Development Methodologies 1. A methodology is: A collection of procedures, techniques, principles, and tools that help developers build a computer.
The Elevator Pitch Kickstand Nov. 8, The Information 1. List your target customer or groups of customers 1. List your target customer or groups.
Agile development By Sam Chamberlain. First a bit of history..
The Agile Inception Deck
THIS IS AGILE? LETITIA FEARON NOR(DEV):CON A BIT ABOUT ME Business Analyst / Agile Trainer Public and Private Sector uk.linkedin.com/in/letitiafearon.
Tietojärjestelmien peruskurssi Software engineering Malin Brännback.
Project Management: A Critical Skill for Organizations Presented by Hetty Baiz Project Office Princeton University.
THE PROCESS OF INTERACTION DESIGN
Chapter 6 The Process of Interaction Design Presented by: Kinnis Gosha, Michael McGill, Jamey White, and Chiao Huang.
Extreme Programming Team Members Gowri Devi Yalamanchi Sandhya Ravi.
EXtreme Programming Quick Introduction Daniel Arraes Pereira Eduardo Lourenço Apolinário Ricardo de Oliveira Cavalcanti.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
COMP 350: Object Oriented Analysis and Design Lecture 2
The Vision Document 1. Importance of a Vision Document  It describes the application in general terms, including descriptions of the target market, the.
Introduction to Agile Methodologies and Concepts Roy Osherove Principal, Team Agile Blog : ISerializable.com.
Product Management 1. The Product Champion  Nearly every successful project has a Product Champion who: Develops the Vision Document. Manages customer.
Requirements Management with Use Cases Module 6: Define the System Requirements Management with Use Cases Module 6: Define the System.
1 BTS330 Vision & Scope. 2 IT Projects What defines project success? On time Within budget Delivers what the clients want The reality Less than 20% of.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Software Development Landscape
Software Engineering Modern Approaches
Copyright David Churchville - XP and Agile Planning David Churchville ExtremePlanner Software XP Fishbowl.
Current Trends in Systems Develpment
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
1 Project Management Introduction. 2 Chap 1 What is the impact? 1994: 16% of IT projects completed “On-Time” 2004 : 29% of IT projects “On- Time” 53%
Project scope and activities INFO 638Lecture #21.
© 2012 About Me Doing agile since 1999 Start ups / Enterprises Planigle - Consulting and Training Qcue – VP, Engineering.
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
CSE 403, Spring 2006, Alverson Pitching Project Ideas Pragmatic Programmer Tip: It’s Both What You Say and the Way You Say It There’s no point in having.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
1 Planning – Agile Style Highsmith, Ch 7 All kinds of iterations! CSSE579 Session 3 Part 1.
The Enterprise Project Management (EPM) Professional March 28th, 2007 Brendan Giles, BSc., PMP, MOS, MCP (EPM) The Key to Successful Adoption of Enterprise.
1 김 수 동 Dept. of Computer Science Soongsil University Tel Fax
Rational Unified Process Mr Hisham AlKhawar. Iterative versus Waterfall  We need to use a life cycle model in order to approach developing a system easily,
UI Panel: Agile User Interface Design Colin Clark.
1 Design and Integration: Part 2. 2 Plus Delta Feedback Reading and lecture repeat Ambiguous questions on quizzes Attendance quizzes Boring white lecture.
The Agile Inception Deck
Copyright © 2015 Curt Hill Software Development Paradigms What do you need to know?
CS3100 Software Project Management Agile Approaches.
Software from Requirements Brent Haines April 12, 2007 Why Methodology Doesn’t Really Matter.
Chapter 7 The Practices: dX. 2 Outline Iterative Development Iterative Development Planning Planning Organizing the Iterations into Management Phases.
Extreme Programming (XP) XP is an agile methodology: –aims to be responsive to change Theme running through XP is the importance of communication –amongst.
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
BA Team: Product Ownership, Analysis, and Solution Design BA Bi-Weekly Mini-meeting March 3, Gathering Requirements On an Agile Project…
Extreme programming (XP) Variant of agile Takes commonsense practices to extreme levels © 2012 by Václav Rajlich1.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Pitching your work Neural networks CSE 481b Lecture 13 February 14, 2006.
Extreme Programming. Extreme Programming (XP) Formulated in 1999 by Kent Beck, Ward Cunningham and Ron Jeffries Agile software development methodology.
Agile. Processes Waterfall Traditional With prototyping Sprial Agile Dynamic Systems Development Method (DSDM) Scrum Crystal eXtreme Programming (XP)
Chapter 10 Information Systems Development. Learning Objectives Upon successful completion of this chapter, you will be able to: Explain the overall process.
10 key principles of agile software development
Yeah but.. What do I do? Software Leadership Dan Fleck 2007.
44222: Information Systems Development
Introduction to Agile. Introduction Who is this guy?
Extreme programming (XP) Advanced Software Engineering Dr Nuha El-Khalili.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Chapter 11 Project Management.
COMP8040 – Cloud Application Frameworks Agile Project Management
CompSci 230 Software Construction
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
The Agile Inception Deck
Training 01: Project Lifecycle & Business Technology Analysis
THE PROCESS OF INTERACTION DESIGN
Agile software development
Presentation transcript:

Agile Samurai Principles

Agile Development

Deliver Value Every Iteration Break big problems into smaller ones Focus on most important issues Deliver something that works Lots of customer feedback Change course when necessary You are accountable

Agile Planning

Agile Lifecycle

Agile Team Blurred instead of fixed roles Characteristics of successful teams – Co-located, at least for initial meetings – Engaged customer – Self-organizing instead of top-down – Accountable and empowered – Cross-functional

What if I don’t have an engaged customer? Build credibility – Find a problem and make it go away – Show you are a fierce executor that will get things done and can help them – Might take a few iterations but they will see your value

The Agile Customer

Agile Development Team

Agile Analyst

Agile Programmer

Agile Tester

Agile Manager

Agile Usability Designer

Kicking off a project The Inception Deck – Ten questions you’d be crazy not to ask before starting any software project – Gets everyone pointing in the same direction Shared goals, vision, context

Inception Deck Collectively fill out a slide on to get a pretty good idea about what the project is, what it isn’t, and what it’s going to take to deliver Need to get customer/stakeholders involved It’s a living document

Why are we here? Important reason #1 Important reason #2 Important reason #3

The elevator pitch For [target customer] who [statement of need or opportunity] the [project name] is a [product category] that [key benefit, compelling reason to buy]. Unlike [primary competitive alternative] our project [statement of primary differentiation].

Product box fun picture

The NOT list IN OUT UNRESOLVED

Your project community Your core team Everyone else !... is always bigger than you think!

Technical solution Danger! Out of scope Technologies: -

What keeps us up at night

Don’t overdo it

The A-Team #RoleCompetencies/Expectations 1AnalystComfortable with just-in-time analysis. Likes to test. Comfortable with rapid iterative development. 2DevelopersC#, MVC.NET, jQuery, SQL Unit testing, refactoring, TDD, continuous integration 0.5Project managerResponsible for outward facing communication Status reports, scope, budget, and reporting upwards

How big is this thing? Ship it! ConstructionUAT Training ~3months 1 wk This is a guess. Not a commitment.

Risk vs. Time The risk of project failure increases over time – think small

The Test

Trade-off sliders The classic four Feature completeness (scope) Stay within budget (budget) Deliver project on time (time) High quality, low defects (quality) ONOFF Other important things Ease of use Community of users Detailed audits (log everything) ONOFF ONOFF ONOFF ONOFF ONOFF ONOFF ONOFF

The first release Ship it! ConstructionUAT Training ~3months 1 wk 3 people, 3 ½ months, $250K