Projects, Assignments, and other Assessments

Slides:



Advertisements
Similar presentations
Keith McMillan Principal, Adept Technologies Copyright (C) 2008, Adept Technologies llc.
Advertisements

Colin Weaver The Eleven Essential Behaviours of Successful Agile Project Teams.
Chapter: 3 Agile Development
E X treme Programming & Agile Modeling Copyright © 2003 Patrick McDermott UC Berkeley Extension
PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
Software Development Methodologies 1. A methodology is: A collection of procedures, techniques, principles, and tools that help developers build a computer.
Slide Set to accompany Web Engineering: A Practitioner’s Approach
Agile Project Management with Scrum
Project Management – An Overview Project as a metaphor – a way to approach a series of activities Contexts – construction managementt, IT development,
Agile Architecture? Paul Lund 24 th Nov Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it.
Agile Methods.
Agile Principles Suradet Jitprapaikulsarn 1. What is Agility? Effective (rapid and adaptive) response to change Effective communication among all stakeholders.
Does it work with Data Warehouses?. “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we.
An Agile View of Process
Introduction to Agile.
Software engineering Process models Pavel Agejkin.
How Agile Are You? Larry Apke Agile Expert
The Two Faces of Project Management Bendik Bygstad, NITH IFI, 25.Sept 2009.
The Two Faces of Project Management Bendik Bygstad, NITH IFI, 16.Sept 2008.
1 Agile Methodology & Programming Ric Holt July 2009.
Software Engineering Modern Approaches
Agile Programming Principles.
The Agile Primer July 2008 © ThoughtWorks 2008.
Agile Web Development C. Daniel Chase University of Colorado at Boulder.
Developed by Reneta Barneva, SUNY Fredonia Agile Development.
Chapter 4 Agile Development
AGILE Methodology. AGILE  derived from the word ‘agile manifesto’, also called the Manifesto for Agile Software Development which is a formal proclamation.
Agile Methods. Agile Process/Method lightweight processes/methods that can be used to manage and control software and product development using iterative,
AgileCamp Presents: Agile 101. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution.
Project Workflow. How do you do it? -Discussion-
CS1: Classic Software Life Cycle “Waterfall” method: 1.Requirements/Analysis Determine the problem to be solved – client-centered 2.Specification.
AGILE COTS Václav Pergl We are uncovering better ways of developing software by doing it and helping others do it. Through this work.
1 11/21/2015 ã 2007, Spencer Rugaber Agile Manifesto February, 2001 XP, SCRUM, DSDM, Adaptive Software Development,
Why (or When) Agile Fails Creating high performance software delivery teams.
Jeff Briggs Senior Consultant Capstone Consulting.
#2-What is Agile? Why Agile? Subtopics 1- Agile motivation for software / systems 2- Agile tenets and principles 3- Agile as a risk mitigation strategy.
- Discussion of Chapter 1 in Martin and Martin.  We are uncovering better ways of developing software by doing it and helping others do it. Through this.
Chapter 3 Agile Development
Module 2: What is Agile? Why use it? TLO: Given a DoD program involved in software development, the student will recognize situations where applying agile.
Agile Introduction Emerson Murphy-Hill. Agile Manifesto/Alliance XP, SCRUM, DSDM, Adaptive Software Development, Crystal, FDD February 2001 (Snowbird,
By: Isuru Abeysekera AGILE DEVELOPMENT. WHAT IS AGILE DEVELOPMENT? Broad term used to describe several methods for a development process Introduced in.
Industrial Software Development Process Bashar Ahmad RISC Software GmbH.
© 2014 IBM Corporation “Leaders Guide to Radical Management” for DevOps with Steve Denning Chapters 6 and 7: From Bureaucracy to Dynamic Linking by Delivering.
Baby Steps to Agility How to Grow Into Agile. A little about me A little about Agile Growing into Agile Questions Goals.
Project Workflow.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Embedded Systems Software Engineering
Chapter 5 Agile Development Moonzoo Kim KAIST
Agile Project Management
Agile Project Management and the yin & yang of
Introduction to Agile Software Development
Principles for Agile Development
Jenna Maghie, Policy Officer
The Agile/Non-Agile Debate
Agile Training Day 2 November 17, 2015.
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Project Workflow.
#2-What is Agile? Why Agile?
Teaching Agile Methods CSEE&T 2017, Savannah, Georgia
Project Management and the Agile Manifesto
Agile Software Development Paradigms
Rosa María Torres de Paz
The Agile Manifesto is based on 12 principles
Introduction to Agile Blue Ocean Workshops.
How Strong is Your Agile Foundation
Adjective: Able to move quickly and easily. Principles and Values
Chapter 3: Agile Software Processes
The Manifesto for Agile Software Development
Agile Development.
Presentation transcript:

Projects, Assignments, and other Assessments

Which of the following are Agile Programming approaches? Advanced System Prototyping XP XT Adaptive Software Development Huddle Scrum

As groups, develop examples of software development Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan When might the other be valuable? Why? Which do you prefer? Why? How would you explain these in your own words? For each of the values, provide at least one example illustrating it.

As a team, put the 13 principles in order by priority Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development Deliver working software frequently Businesspeople and developers must work together daily throughout the project Build projects around motivated individuals. Given the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation Working software is the primary measure of progress Agile processes promote sustainable development The sponsors, developers, and users should be able to maintain a constant pace indefinitely (Not in all lists) Continuous attention to technical excellence and good design enhances agility Simplicity – the art of maximizing the amount of work not done – is essential The best architectures, requirements, and designs emerge from self organizing teams At regular intervals, the team reflects on how to become more effective, then tunes and adjust its behavior accordingly. Can you discard one? If you were going to add a principle, what would it be?

As a team, list the five most important reasons to use agile methods

As a team, list the five most important reasons NOT to use agile methods

Adoption Assessment Matrix Adoption Assessment Matrix Weight Rank Result Duration of the project Acceptance of change Criticality of project Team size Skill level of team Location of customer Customer involvement Organizational and reporting structure Process Documentation requirements Layout of workplace As a team, fill in the adoption assessment matrix. What weight (1-5) do you give each factor? For a specific project, what rank would you assess?

A Class Project: Putting the Agile principles and practices in context Consider the Agile Manifesto, principles and practices. What are the Disciplined principles and practices? How do you personally weight these items? How do you think companies weight them? Consider three groups: developers, companies, and users. Why would these principles or practices be important to them? What do they want?

As a team, discuss how the agile values and practices help with these problems Requirements are not clearly communicated Requirements do not solve the business problem Requirements change prior to the completion of the project Software (code) has not been tested Software has not been tested as the user will use it Software developed so that it is difficult to modify Software used for functions for which it was not intended Projects not staffed with resources required Schedule and scope commitments made before understanding requirements or technical risks Lindstrom and Jeffries (2004)

Paper Write a paper examining Reasons projects fail How agile development addresses this Other benefits and drawbacks to using agile development

Project Develop a plan for introducing agile development methods in an industrial setting Include publicity, training, changes in organizational processes and procedures, and any other impacts Provide a business case supporting this change

Project Design a research plan to investigate some aspect of agile development What is your hypothesis? What will you measure and how? What do you expect to learn? Where would you publish your results?