Creator: ACSession No: 19 Slide No: 1Reviewer: - CSE300Advanced Software EngineeringMarch 2007 ‘Agile Methods’ (part 2) CSE300 Advanced Software Engineering.

Slides:



Advertisements
Similar presentations
Software development process improvement Ville Wettenhovi Master thesis presentation Supervisor:Professor Jukka Manner Instructor:M.Sc. Markus Aalto Date:23th.
Advertisements

What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Sharif University of Technology Session # 3.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
ITEC 370 Lecture 25 Lifecycles. Review Questions? F give prototype demonstration –Testing plan for your software Life cycles –Scrum (Roles, Meetings,
Agile Development.
Agile methods and techniques– some method comparisons Dave Parsons Mark Cranshaw.
NAUG NAUG Knowledge Evening – th February 2007.
 User assignments (product owner)  ‘circle’  1 st sprint: ◦ Scrum Boards (informative workspace)  Product -, release -, sprint -, defect backlog 
Agile Process Models. Prescriptive models don’t work It is unrealistic to not have changes. Why? The Agile Manifesto: Individuals and interactions over.
Software Life Cycles ECE 417/617: Elements of Software Engineering
Agile
6 December ’s  60’s “Cowboys” wrote software anyway that they could Difference between best programmers and worst as high as 28:1 (many sources)
Agile Software Development. Traditional Software Development 1.Initiation (RFP) 2.Feasibility study Technical – can we build it? Economic – should we.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Extreme Programming--a “New” Process Model Extreme Programming-- a “New” Process Model.
Creator: ACSession No: 12 Slide No: 1Reviewer: CSE300Advanced Software EngineeringJanuary 2006 Testing Strategy CSE300 Advanced Software Engineering University.
Creator: ACSession No: 9 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringNovember 2005 Risk Management CSE300 Advanced Software Engineering.
Creator: ACSession No: 10 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringDecember 2005 Project Management CSE300 Advanced Software Engineering.
Software Engineering Lecture No:12. Lecture # 7
Introduction to Agile Methodologies and Concepts Roy Osherove Principal, Team Agile Blog : ISerializable.com.
Introduction to Agile.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
Dr. Tom WayCSC Software Processes CSC 4700 Software Engineering.
Sofia Bulgaria Summer School IST eXPERT: Best Practice on e-Project Development 30 June - 2 July 2003 eXtreme programming.
Current Trends in Systems Develpment
Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
Embracing change with Extreme Programming Method Engineering Erik ten Brinke
Agile Methodologies: Comparative Study and Future Direction 林佳蓁 資工 4B.
Creator: ACSession No: 16 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringFebruary 2006 (Software Quality) Configuration Management CSE300 Advanced.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky.
Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
4/23/ :45 PM © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered.
Creator: ACSession No: 15 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringFebruary 2006 Software Quality Assurance & Software Quality Control.
Extreme Programming (XP). Agile Software Development Paradigm Values individuals and interactions over processes and tools. Values working software over.
Agile
Coming up: The Manifesto for Agile Software Development 1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 3 Agile Development Software Engineering:
Implementing XP at PUT Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
XP Overview Short Life cycle Risky / Dynamic Requirements Increase developer productivity.
K.Ingram 1 Sept 2007 Agile Software Development. K.Ingram 2 Sept 2007 Contents Agile Software Development: 1.What is it? 2.Agile’s Values, Principles,
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 4 Agile Development Discussion of Agile Development and Agile Process.
Basic Approach Development driven by time boxing May sacrifice requirements in order to keep schedule (time boxed) Steer project as you go based on user.
Creator: ACSession No: 7 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringSeptember 2005 Software Measurement – Estimation and Productivity CSE300.
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
Chapter 3 Agile Development
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
Agile. Processes Waterfall Traditional With prototyping Sprial Agile Dynamic Systems Development Method (DSDM) Scrum Crystal eXtreme Programming (XP)
It’s Agile …. like! A Corkman’s introduction to Agile software delivery.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Teaching slides Chapter 2. Chapter 2 Software Engineering Methodologies Introduction Why a methodology? Agile methodologies Waterfall model Rational Unified.
Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,
Extreme Programming מתודולוגיה לפיתוח פרויקטי תוכנה.
Extreme programming (XP) Advanced Software Engineering Dr Nuha El-Khalili.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.
Requirements Engineering Lecture 4
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Appendix B Agile Methodologies
Planning User stories are written.
Agile Software Development Brian Moseley.
Approaches to Systems Development
روش‌های سريع الانتقال (چابک) توسعه نرم افزار
What do you need to know about XP?
How to Successfully Implement an Agile Project
Appendix B Agile Methodologies
Agile software development
Presentation transcript:

Creator: ACSession No: 19 Slide No: 1Reviewer: - CSE300Advanced Software EngineeringMarch 2007 ‘Agile Methods’ (part 2) CSE300 Advanced Software Engineering University of Sunderland © 2006 Anne Comer

CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 2Reviewer: - Agile Development – the Difference All software development methods, including the Agile ones, have some sort of underlying project life cycle. The key elements are a Project Initiation and Project Plan followed by one or more Releases made up of timeboxes. Optional phases of Elaborate Requirements, & Architecture. The generic ‘Agile Life Cycle’

CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 3Reviewer: - Is Agile Good Project Management? Aspects of project management (Watson (1998)) Project Initiation Project Planning, Estimating and Budgeting Roles and Responsibilities Controlling the Project Managing Change Managing Quality Managing Risk Reviewing the Project

CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 4Reviewer: - Project Initiation Scope Project Choose the right method Choose your formality Define a vision to point the way High Level Requirements - Fast

CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 5Reviewer: - Project Planning, Estimating and Budgeting Planning based on Timeboxes Developers do initial project estimates No contingency in developer estimates Project Plan = Requirements in Timeboxes Timebox Plan built by team

CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 6Reviewer: - Roles and Responsibilities Small Cross-functional teams Agile Developer – generalist User/Customer – An Active Role Project Manager as Shepherd

CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 7Reviewer: - Controlling the Project Produce Product quality releases Simple and direct communication is key –Intra-team communication –Inter-team communication –Management reporting

CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 8Reviewer: - Managing Change Time is more important than functionality Minor changes accepted in a timebox Big changes outside a timebox customer can add/change any requirement developers re-estimate customer trades off requirements Big changes inside a timebox either isn’t allowed at all or customer trades functionality in/out of timebox.

CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 9Reviewer: - Managing Quality Stated ‘Quality Goals’ / addressed continuously Peer Review (mandatory XP (pair programming) / common in DSDM) XP – must have tests before code Integration Testing continuous & automatic, daily build & smoke test. (XP, Scrum) User Acceptance Testing –UAT during development (XP, DSDM) –formal reviews during timebox (DSDM) and at end (XP, Scrum, DSDM) Extra testing activities (e.g., performance testing) - - scheduled in the same way as requirements

CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 10Reviewer: - Risk Management (RM) DSDM explicitly demands RM procedure Agile process reduces level of 5 of top 10 risks –Feature creep –Gold plating –Short changed quality –Overly optimistic estimates –Friction between developers and customers Technical risk addressed by –“prototypes” (DSDM) –“spike solutions” (XP)

CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 11Reviewer: - Project Review Inside the project (self adapting) –1or2 hours reflection each Iteration (timebox) XP The next project –Story Pile (XP) –Product Backlog (Scrum) –Project Review Document (DSDM).

CSE300Advanced Software EngineeringMarch 2007 Creator/Editor: ACSession No:19 Slide No: 12Reviewer: - Review Mainly design for today and ‘refactor’ tomorrow Only DSDM makes an architecture phase compulsory Agile Development is a set of practices and guidelines Agility can be good Project Management