1 Agile Software Engineering Practice to Improve Project Success Dietmar Winkler Vienna University of Technology Institute of Software Technology and Interactive Systems
2 Motivation The construction of high-quality software products requires (a) professional approaches (software processes), an appropriate set of methods, and welltrained engineers. Rapid and late changing requirements are success-critical challenges in common industrial projects because they have a strong impact on product quality, design, and project schedule. Question How can we address unclear, rapid and late changing requirements in (industry) software projects? Topics Structured Software Engineering Processes (e.g., V-Modell XT). Agile Software Development Processes (e.g, SCRUM). Software Development Practices (MDD / TDD / Pair Programming) 2
3 Why Requirements are Important The hardest single part of building a system is deciding what do build. (B.W. Boehm, 1997) Requirements represent the needs of the customer (what does he need?) from user/customer point of view. Requirements contribute to the solution of a real-world-problem. [SWEBOK, 2004] A requirement is an expression of desired behavior from user perspective. Requirements management is the science and art of gathering and managing user, business, technical, and functional requirements within a product development project. Requirements management deals with a set of requirements to handle complex systems. Note: Requirements must be auditable and testable!
4 Impact of Requirements Reasons for project interruption - survey including 365 industrial responses (8.380 applications) [Chaos Report, 1994]: 1. Incomplete requirements (13.1%) 2. Lack of User Involvement (12.4%) 6. Changing Requirements and Specifications (8.7%) Selection of Top-Ten risk items for project failure [Boehm, 1991] 3) Developing wrong software functions. 4) Developing the wrong user interfaces. 5) Gold plating. 6) Continuing stream of requirement changes. Software Processes help to address requirements elicitation.
5 Software Life-Cycle The Software Life Cycle is a general purpose process including all process steps from the first idea to the retirement of a software product. A Software Process is a subset of the life cycle approach and defines the sequence of steps within the project course. Support of Software / Systems Development. Provide consistent guidelines, method and tool support, embedded within the process. In common industrial practice, several different software processes emerged: Focus on specific application domains and project types. Limited to specific types of products and their attributes. Need for selection criteria for software processes.
6 Structured Software Engineering Processes Example: V-Modell (XT) Pro: Specification vs. Realization and Testing. Focus on deliverables (products) Different levels of abstraction (user, architects, programmers). Defect detection and prevention in early stages of development. idea / study system specification system design module specification acceptance test user view integration test archetectural view module test Con: Clear definition of system requirements necessary. Well-known application domain required. Focus on documentation (Documentation overhead). Critical on defects in early stages of software development. implementing view tested design/system tested modules operation / maintenance installed system Application: Large projects with clear defined goals and requirements.
7 Incremental Software Development analysis design Implementation / integration Product delivery Build 1 analysis design Implementation / integration Product delivery Build 2 analysis design Implementation / integration Product delivery Build 3 analysis design Implementation / integration Product delivery Note: analysis team design team implementation team Build n
8 Incremental Software Development Stepwise product development (several releases, builds) Continuous integration phases Small steps of development (planning of software increments) Planning of iterations including milestone definition after each development cycle. PRO Unclear requirements. long development duration. Quick delivery of (parts) of the system to customers. CON Problems, if releases will not fit together. Application Large and complex software systems. Project with long development duration
9 Some Questions Structured and systematic software processes define the sequence of steps within a project course. Is it always possible / reasonable to follow a strict process? Does a structured process address rapid/late changing requirements? Structured processes (e.g., the V-Model 97) require comprehensive documentation. Is a comprehensive documentation necessary all the time? Structured processes allow a detailed project plan because of the predefined steps over the whole project. What happens, if modified/additional requirements occur in later stages of development? Typically software projects are based on contracts (based on a detailed specification).
10 Agile SE Approaches 1 4 Key Value Aspects of Agile Software Development Individuals and interaction over processes and tools Working software over comprehensive documentation. Customer Collaboration over contract negotiation Responding to change over following a plan. Key Principles (Selection): Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in the development. Deliver working software frequently. Collaboration of business people and developers. Simplicity of the solution. The best architectures, requirements, and designs emerge from selforganizing teams. etc. 1
11 SCRUM Agile Software Process from Project Management (PM) view. SCRUM is not an acronym; it is based on the scrum formation in Rugby sports. Characteristics: One team builds one unit. Clear distribution of work. Clear priorities of project deliverables (backlog items). One common goal (= delivery of the product) A Sprint is a central element. Temporal structure = daily Scrum Meeting + Review + Retrospective. Basic Roles: Product Owner (Self-organizing) Team Scrum Master
12 SCRUM Phases PRE-GAME SPRINT POST-GAME
13 SCRUM Sprints Scrum represents a set of procedures, roles and methods for project management. Agile software development Self-organizing teams.
14 SCRUM Definition of terms Backlog: All work to be performed in the near future, both well defined and requiring further definition. Sprint: A period of 30 days or less where a set of work will be performed to create a deliverable. Sprint Backlog: A set of defined work packages for a sprint duration of about 1 month (incremental deliverables). No or only a few changes are possible. Scrum: A daily meeting for progress discussion to clarify questions and to remove obscurities. Scrum Meeting rules: Protocol for effective Scrum daily meetings. Scrum Team: The cross-functional team working on the sprint's backlog. Burndown Chart: Graph that represents the project progress.
15 Agile Practices Software processes require suitable methods to support engineers in constructing high-quality software products, e.g., Model-Driven Development. Test-Driven Development. Pair Programming.
16 Model-Driven Development Software Engineering requires die construction of consistent views on the system. Models support to keep an overview on the system and its components. Basis for effective and efficient team work. Common notation (language) and consistent meaning (different stakeholders / domains typically use their own language ) Basis for automation (e.g., automated code generation, test case generation, testing, etc.) Examples (based on the UML 2 1 diagram family): 6 Structural diagrams: e.g., component, package, and class diagrams 3 Behavioral diagrams, e.g., activity diagrams, state charts, use cases. 4 Interaction diagrams, e.g., sequence and timing diagrams. UML = Unified Modelling Language
17 UML 2 - Examples Logical Perspective Use Case Perspective Customer Need Deployment Perspective Process Perspective Requirements & Use Case Description Implementation Perspective Data model > Notation for Modeling a System > describes statical and dynamical aspects > Note: Perspective selection depends on the type of the system
18 Model Driven Development Description of real-world problems in a common language (e.g., UML notation). Basis for communication between consumers and developers. Translation From models to artifacts (e.g., code) From models to other models Etc. Basis for automation (e.g., deriving software code and test cases based on models)
19 Test-Driven Development (TDD) Goal: Every feature in an application that gets implemented has to be testable. Testing either automatically using unit tests, automated UI tests, etc. or manually executed by following a predefined test plan. Test comes before or parallel to the implementation. Traditional Testing Approaches based on test strategies and plans: Shorter Cycles are quite better.
21 Test-Driven Development (TDD) Unit Tests: construction of executable test cases. Derive assertions for test case execution (expected results) Normal case: should be handled without problems. correct defect : should be handled by the system (predictable exception handling) Basic TDD Process : Identify the component / class Write Test cases (e.g., JUnit) Execute Test cases Test cases should fail Implement the component/class Execute Test cases Test cases should be successful. Cleanup code
22 Pair Programming Pair Programming (PP) is a common practice in the area of agile software engineering. PP focuses on the construction of software code. PP involves two engineers ( Power of Two Brains ). Typical Roles and tasks Driver: responsible for code implementation. Observer: supports the driver by observing his activities. keeper of the focus and the pace of the current tasks. performs implicit quality assurance activities (e.g., continuous reviews) The role assignment (driver and observer) should change frequently.
23 Pair Programming Pros & Cons Reported benefits of PP vs. Solo Programming More disciplined (2 persons involved) Improved software code and higher code quality (implicit quality assurance) Improved productivity (change of roles) Collective code ownership (2 persons involved) Mentoring & learning (e.g., senior/junior as pair ), But Additional effort (2 persons involved) Possible authority problems. Team building might be difficult Copyright issues What are the deliverables of the observer? Nevertheless, PP is a promising approach for the delivery of high-quality software products (e.g., reported from industry and academic studies)
24 Next Steps in Pair Programming 1? Pair X : Enhancing Pair Programming. Application of Pairs to other software engineering activities, e.g., Pair Requirements Analysis, Pair Design, Pair Testing Will the involvement of two persons increase productivity and quality in these areas? Are pair activities facilitators for learning, training and mentoring of juniors? Empirical studies will provide answers to this question. IPP: Integrated Pair Programming Extending Pair Programming with systematic Quality Assurance to enable repeatable, traceable and auditable software products required by several application domains e.g., security and safety-critical systems. Currently, the deliverables of the observer are unclear. Systematic QA (e.g., inspection) enable traceable, repeatable, and auditable software products. The integration of constructive and analyitical method might bring up benefits of different disciplines. 1 Ongoing / planned projects at TUW.
25 Summary Software Processes: Requirements are success-critical in software engineering projects. Structured software processes typically require stable requirements because of a sequential order of process steps with limitations of process backtracking. Agile approaches focus on a tight customer involvement, small iterations and support frequent changing requirements. Agile Practices: Models present real-world scenarios, support communication between consumers and developers (common language), and are the basis for automation (e.g., automated code generation based on models). Test-Driven Development (TDD) focuses on the generation of test cases before or (at least) in parallel to the development of software code. Pair Programming is a team activity - involving two persons - to increase productivity and software quality and supports learning. The application of agile software development processes and practices promises to support the construction of high-quality software products with respect to frequent changing requirements.
26 References Books & Papers: Boehm B.: Software Risk Management: Principles and Practices, IEEE Software 8(1), pp32-41, Kappel G.: On Models and Ontologies or what you always wanted to know about Model-Driven Engineering, Keynote SEE Conference, Munich, Sommerville I: Software Engineering, 7th edition, Williams L, Kessler R, All I really need to know about pair programming I learned in Kindergarten, in Communication of the ACM 43(5), Web References: Schwaber Ken: SCRUM Development Process, Software Engineering Body of Knowledge, Software Engineering Best practices: V-Modell XT;
27 Thank you for your attention Contact: Dipl.-Ing. Dietmar Winkler Vienna University of Technology Institute of Software Technology and Interactive Systems Favoritenstr. 9-11/188, A-1040 Vienna, Austria
28 This research work has been supported by a Marie Curie Transfer of Knowledge Fellowship of the European Community's 6th Framework Programme under the contract MTKD-CT : CzechVMXT.
Best-Practice Software Engineering: Software Processes to Support Project Success Dietmar Winkler Vienna University of Technology Institute of Software Technology and Interactive Systems Dietmar.Winkler@qse.ifs.tuwien.ac.at
Empirical Software Engineering Introduction & Basic Concepts Dietmar Winkler Vienna University of Technology Institute of Software Technology and Interactive Systems firstname.lastname@example.org
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 Software Development Methodologies and Its Quality Assurance Aslin Jenila.P.S Assistant Professor, Hindustan University, Chennai Abstract: Agility, with regard to software development, can be expressed
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
Introduction to Agile Software Development Word Association Write down the first word or phrase that pops in your head when you hear: Extreme Programming (XP) Team (or Personal) Software Process (TSP/PSP)
Agile Scrum Workshop What is agile and scrum? Agile meaning: Able to move quickly and easily. Scrum meaning: a Rugby play Agile Scrum: It is an iterative and incremental agile software development framework
Quality Assurance in an Agile Environment 1 Discussion Topic The Agile Movement Transition of QA practice and methods to Agile from Traditional Scrum and QA Recap Open Discussion www.emids.com 2 What is
Agile Project Management with Scrum Resource links http://www.agilealliance.org/ http://www.agilemanifesto.org/ http://www.scrum-master.com/ 1 Manifesto for Agile Software Development Individuals and interactions
Process Automation and Quality Management in Multi-Disciplinary Engineering Environments Stefan Biffl Dietmar Winkler Christian Doppler Laboratory SE-Flex-AS Institute of Software Technology and Interactive
Issues in Internet Design and Development Course of Instructions on Issues in Internet Design and Development Week-2 Agile Methods Saad Bin Saleem PhD Candidate (Software Engineering) Users.mct.open.ac.uk/sbs85
Early Software Product Improvement with Sequential Inspection Sessions: An empirical Investigation of Inspector Capability and Learning Effects Dietmar Winkler, Bettina Thurnher, Stefan Biffl Institute
1 Software Engineering Lecture 2: Software Life Cycles Stefan Hallerstede Århus School of Engineering 25 August 2011 2 Contents Naive Software Development Code & Fix Towards A Software Process Software
Scrum: A disciplined approach to product quality and project success. CQAA February 23, 2011 Patricia Rotman Introductions Copyright 2011-2 Alternate Titles Considered Scrum: Just do it! Scrum: It only
CS4507 Advanced Software Engineering Lectures 2 & 3: Software Development Lifecycle Models A O Riordan, 2015 Some diagrams from Sommerville, some notes from Maciaszek/Liong Lifecycle Model Software development
Software Engineering Prof. N. L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture - 2 Introduction to Software Engineering Challenges, Process Models etc (Part 2) This
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
Agile Project Management By Mark C. Layton Agile project management focuses on continuous improvement, scope flexibility, team input, and delivering essential quality products. Agile project management
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...
1 W E B B A S E D M E E T I N G S C H E D U L E R S Y S T E M Project Plan Version 4.0 CS 6361 ADVANCED REQUIREMENTS ENGINEERING, SPRING 2010 UNIVERSITY OF TEXAS AT DALLAS R E Q U I R E M E N T S E N G
Test-Driven Automation: Adopting Test-First Development to Improve Automation Systems Engineering Processes Dietmar Winkler Stefan Biffl Thomas Östreicher Institute of Software Technology and Interactive
A Cynical View on Agile Software Development from the Perspective of a new Small-Scale Software Industry Apoorva Mishra Computer Science & Engineering C.S.I.T, Durg, India Deepty Dubey Computer Science
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
What is Scrum? From http://www.scrumalliance.org/pages/what_is_scrum A lean approach to software development Scrum is an agile software development framework. Work is structured in cycles of work called
Investigating the Temporal Behavior of Defect Detection in Software Inspection and Inspection-Based Testing Dietmar Winkler Stefan Biffl Kevin Faderl Institute of Software Technology and Interactive Systems,
PLM - Agile Agile Development Evolved in the 1990s as a response to heavyweight methodologies. In 2001 representatives of various new methodologies met to discuss the need for lighter alternatives. The
Sample Questions EXIN Agile Scrum Foundation Edition September 2013 Copyright 2013 EXIN All rights reserved. No part of this publication may be published, reproduced, copied or stored in a data processing
Agile Systems Engineering: What is it and What Have We Learned? March 2012 Dr. Suzette S. Johnson Agile Engineering Northrop Grumman Suzette.Johnson@ngc.com Getting To Know You! Dr. Suzette Johnson Northrop
XP & Scrum Beatrice Åkerblom email@example.com extreme Programming XP Roles XP Roles, cont!d! Customer ~ Writes User Stories and specifies Functional Tests ~ Sets priorities, explains stories ~ May or
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
Traditional SDLC Vs Scrum Methodology A Comparative Study M. Mahalakshmi 1, DR. M. Sundararajan 2 1 Research Scholar, St. Peter s University, Avadi, India 2 Asst. Professor, Department of Computer Science,
Scrum and Testing The end of the test role Bryan Bakker 20 maart 2012 voordracht georganiseerd door Discussiegroep Software Testing met de steun van Ingenieurshuis, Antwerpen Scrum and Testing... The end
Software Development Process A software development process, also known as software development lifecycle, is a structure imposed on the development of a software product. Similar terms include software
CIMCA 2008, IAWTIC 2008, and ISE 2008 Comparing Agile Software Processes Based on the Software Development Project Requirements Malik Qasaimeh, Hossein Mehrfard, Abdelwahab Hamou-Lhadj Department of Electrical
Theory Lecture Plan 2 Software Configuration Lecture 11 Software Engineering TDDC88/TDDC93 autumn 2008 Department of Computer and Information Science Linköping University, Sweden L1 - Course Introduction
PROCESS OF MOVING FROM WATERFALL TO AGILE PROJECT MANAGEMENT MODEL Sanja Vukićević 1, Dražen Drašković 2 1 Faculty of Organizational Sciences, University of Belgrade, firstname.lastname@example.org 2 Faculty
Ingegneria del Software Corso di Laurea in Informatica per il Management Agile software development Davide Rossi Dipartimento di Informatica Università di Bologna The problem Efficiency: too much effort
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
Slide 6.1 System development lifecycle waterfall model Figure 6.1 The waterfall model of system development lifecycle Slide 6.2 The b model Figure 6.2 The b model Source: N D Birrell and M A Ould, A Practical
Introduction to Software Engineering: Overview and Methodologies John T. Bell Department of Computer Science University of Illinois, Chicago Based on materials from Bruegge & DuToit, Object Oriented Software
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
Scrum SE Presentation by Anurag Dodeja Spring 2010 What is Scrum? Scrum is an agile software development framework. Work is structured in cycles of work called sprints, iterations of work that are typically
Agile Metrics It s Not All That Complicated Welcome About your Trainer, Katia Sullivan VersionOne Product Trainer and Agile Coach Certified Scrum Master Certified Scrum Product Owner Led teams/org s to
BIO PRESENTATION W3 6/28/ 11:30 AM RISK MANAGMENT ON AN AGILE PROJECT Michele Sliger Rally Software Development Better Software Conference June 26 29, Las Vegas, NV USA Michele Sliger Michele Sliger has
Testing in Agile methodologies easier or more difficult? Lucjan Stapp Warsaw University of Technology Stowarzyszenie Jakości Systemów Informatycznych L.Stapp@mini.pw.edu.pl L.Stapp@sjsi.org Professor in
Agile Testing Tiina Kiuru Reaktor Innovations 08.10.08 1 Agenda What is agile? Agile values, principles and practices How to organize testing? How to implement testing? 08.10.08 2 What is agile? 08.10.08
T h e R e s e a r c h B u l l e t i n o f J o r d a n A C M, I S S N : 2 0 7 8-7 9 5 2, V o l u m e I I ( I I I ) P a g e 74 Suggested Framework for Agile MDA and Agile Methodologies Dr. Asim El-Sheikh
What is a life cycle model? Framework under which a software product is going to be developed. Defines the phases that the product under development will go through. Identifies activities involved in each
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
Software Process in Modern Software Development Lecture 3 Software Engineering i Practice Software engineering practice is a broad array of principles, concepts, methods, and tools that must be considered
Agile and Secure: Can We Be Both? OWASP AppSec Seattle Oct 2006 Keith Landrus Director of Technology Denim Group Ltd. email@example.com (210) 572-4400 Copyright 2006 - The OWASP Foundation Permission
Sample Exam ISTQB Agile Foundation Questions Exam Prepared By Released August 2016 1 #1 Which of the following is the correct pairing according to the Agile Manifesto statement of values? a. Individuals
Nova Software Quality Assurance Process White Paper Atlantic International Building 15F No.2 Ke Yuan Yi Road, Shiqiaopu, Chongqing, P.R.C. 400039 Tel: 86-23- 68795169 Fax: 86-23- 68795169 Quality Assurance
October 28, 2015 Verification & Validation In many computer science courses, software is submitted once, graded, and thrown away. In real life, software development is an process. Some attempts to codify
, pp.75-86 http://dx.doi.org/10.14257/ijast.2013.58.07 An Appraisal of Agile Software Development Process Muhammad Amir 1, Khalid Khan 2, Adnan Khan 3 and M.N.A. Khan 4 1,2,3,4 Department of Computing,
T-76.650 SEMINAR IN SOFTWARE ENGINEERING, SPRING 2004 1 An Overview of Quality Assurance Practices in Agile Methodologies Olli P. Timperi Abstract The focus of literature and debates of agile methodologies
Development Process Quick Guide METHODOLOGY Every project is unique You know your business inside out. You have thought and planned your ideas carefully and are keen to see it live as soon as possible.
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC) ANALYTICAL COMPARISON AND SURVEY ON TRADITIONAL AND AGILE METHODOLOGY Sujit Kumar Dora 1 and Pushkar Dubey 2 1 Programmer, Computer Science & Engineering, Padmashree
Agile Processes and Methodologies: A Conceptual Study Sheetal Sharma Amity School of Engineering & Technology Amity University Noida Sheetal.firstname.lastname@example.org Darothi Sarkar Amity School of Engineering &
A S P E S D L C Tr a i n i n g ScrumMaster Certification Workshop: Preparatory Reading A WHITE PAPER PROVIDED BY ASPE ScrumMaster Certification Workshop: Preparatory Reading Greetings, Potential Certified
The current issue and full text archive of this journal is available at www.emeraldinsight.com/1065-075x.htm OCLC 18 Accepted October 2010 MANAGING DIGITAL LIBRARIES: THE VIEW FROM 30,000 FEET Understanding
An SME Transition from Plan-Driven to Hybrid Project Management with Agile Software Development Methods Stefan Biffl 1 Richard Mordinyi 1 Günter Raidl 2 Heinrich Steininger 2 Dietmar Winkler 1 1 TU Vienna,
Journal of Software Engineering and Applications, 2013, 6, 59-64 http://dx.doi.org/10.4236/jsea.2013.62010 Published Online February 2013 (http://www.scirp.org/journal/jsea) 59 Case Study on Critical Success
A Viable Systems Engineering Approach Presented by: Dick Carlson (email@example.com) Philip Matuzic (firstname.lastname@example.org) i i Introduction This presentation ti addresses systems engineering
AGILE METHODOLOGY IN SOFTWARE DEVELOPMENT Shivangi Shandilya, Surekha Sangwan, Ritu Yadav Dept. of Computer Science Engineering Dronacharya College Of Engineering, Gurgaon Abstract- Looking at the software
Agile QA s Revolutionary Impact on Project Management Introduction & Agenda Rachele Maurer Agile Coach, Platinum Edge Inc. PMP, CSM, PMI-ACP Agenda A quick overview of agile Current QA practices QA using
6 Contracts and Scenarios in the Software Development Process Summary: Software development processes play an important role in the successful and timely delivery of software. There are different approaches
Agile Testing (October 2011) Page 1 Learning Objectives for Agile Testing "Certification is the by-product; Learning is the product." Agile Testing should: Compare and contrast agile testing with traditional
Software Process Improvement Initiatives based on Quality Assurance Strategies: A QATAM Pilot Application Dietmar Winkler 1, Frank Elberzhager 2, Stefan Biffl 1, Robert Eschbach 2 1 Christian Doppler Laboratory
Agile Methodologies XP and Scrum Introduction into Software Engineering Lecture 22 Bernd Bruegge Applied Software Engineering Technische Universitaet Muenchen 1 Problem: How to we Control Software Development?
Scaling Scrum Colin Bird & Rachel Davies Scrum Gathering London 2007 Scrum on a Slide Does Scrum Scale? Ok, so Scrum is great for a small team but what happens when you have to work on a big project? Large
Learn. Inspect. Adapt: An Overview of Agile Project Delivery Doug Rosenberg and Kara Silva June 19, 2008 Paper Airplanes! The Agile Manifesto We are uncovering better ways of developing software by doing
Agile with XP and Scrum Amit Goel National Agile Software Workshop @ Indore Agile India Conference Agile Software Community of India Disclaimer and Credits Most of material in this presentation has been
Agile Project Management Overview Fabrizio Morando Application Development Manager martedì 20 novembre 2012 What is Agile? Agile is used to denote the ability of Agile Methods to respond to changing requirement
Agile Development: Demystified by Scott Warner Sprint, Agile, Scrum - words we normally associate with sports. Agile Methodology is 1 very much [like ] a sport with a highly-structured, rules-based engagement
IBM Software Group Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK Jean-Louis Maréchaux Software IT Specialist IBM Rational
PointZERO Enabling the right first time principle Antwerpen, 16 May 2013 Geert Vanhove Rik Marselis Consumerization of IT Cloud Big data Mobility bl Social 1 Major causes of both cost and time overruns
Case Study Software Development with Agile Methods Introduction: Web application development is a much studied, heavily practiced activity. That is, capturing and validating user requirements, estimating
Transdyne Corporation CMMI Implementations in Small & Medium Organizations Using the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects Dana Roberson Quality Software Engineer NNSA Service
PERFORMANCE ENGINEERING IN SCRUM Balasubramanian, Infosys Technologies Limited This paper describes how performance engineering as a software discipline should be planned and executed in an agile development
Volume 4, Issue 4, April 2014 ISSN: 2277 128X International Journal of Advanced Research in Computer Science and Software Engineering Research Paper Available online at: www.ijarcsse.com A Document Driven