Agile Software Development Practice Adoption Survey Narendra Kurapati, Venkata Sarath Chandra Manyam, and Kai Petersen Blekinge Institute of Technology.

Slides:

Advertisements

Similar presentations

Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger

Advertisements

Workshop: Professional Development of Software Engineers Hazzan Orit Department of Education in Technology and Scinece Technion – Israel Institute of Technology.

ITEC 370 Lecture 25 Lifecycles. Review Questions? F give prototype demonstration –Testing plan for your software Life cycles –Scrum (Roles, Meetings,

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.

© ThoughtWorks, 2008 Improving Productivity and Quality With Agile Patrick Kua.

Radu Poenaru Ijaz Ahmet

XP – eXtreme Programming A gentle introduction. Cleviton Vinícius Jobson Ronan Thiago Rodrigues.

Agile Methodology: The New Wave in Software Development By Patricia Cleary Thesis Hypothesis: The agile methodologies are better than the current methodology.

EXtreme Programming Quick Introduction Daniel Arraes Pereira Eduardo Lourenço Apolinário Ricardo de Oliveira Cavalcanti.

Extreme Programming Mark Steverson. What Is Extreme Programming? ● Extreme Programming (XP) is a lightweight, agile methodology developed by Kent Beck.

Transitioning to XP or The Fanciful Opinions of Don Wells.

Extreme Programming--a “New” Process Model Extreme Programming-- a “New” Process Model.

Introduction to Agile Methodologies and Concepts Roy Osherove Principal, Team Agile Blog : ISerializable.com.

Introduction to Agile.

An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.

1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.

Agile Software Development What is Agile? And How are we implementing Agile?

Configuration Issues and Efforts for Configuring Agile Approaches-Situational based Method Engineering Rinky Dwivedi, Computer Engineering Department Delhi.

Software Engineering Modern Approaches

Chapter 5 Software Process Models. Problems with “Traditional” Processes 1.Focused on and oriented towards “large projects” and lengthy development time.

Sofia Bulgaria Summer School IST eXPERT: Best Practice on e-Project Development 30 June - 2 July 2003 eXtreme programming.

Software Development and Release Management By James Lawrence Software Development Manager.

Current Trends in Systems Develpment

SE-280 Dr. Mark L. Hornick 1 Process Adaptations.

Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.

Embracing change with Extreme Programming Method Engineering Erik ten Brinke

Unified Process versus Extreme Programming. Outline Compare and contrast UP and XP  Processes / Disciplines  Management  Artefacts Risk management.

1 Extreme Programming Practices The Planning Game Small Releases System Metaphor Simple Design Continuous Testing Refactoring Pair Programming Collective.

Copyright © by Mark J. Sebern Software Engineering Process I SE Sprint Execution.

EXtreme Programming: An Introduction Presentation by: Jon Banta.

Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.

Extreme Programming (XP). Agile Software Development Paradigm Values individuals and interactions over processes and tools. Values working software over.

Extreme Programming.

XP – Extreme Programming

Informatics 43 – May 14, Open Source Source code is freely available and (usually) re-distributable Examples: Firefox web browser Apache HTTP Server.

December Using Software Development Methodology (SDM) in the Third Teaching Unit (laboratory) CS Teachers Conference Dr. Orit Hazzan & Yael Dubinsky.

The Confounding World of Process Methodologies By Thelma Hataria.

Copyright © 2015 Curt Hill Software Development Paradigms What do you need to know?

CS3100 Software Project Management Agile Approaches.

AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.

Agile Methodology Paul Mohrbacher. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through.

Extreme Programming Based on and

Extreme programming (XP) Variant of agile Takes commonsense practices to extreme levels © 2012 by Václav Rajlich1.

Extreme Programming. Extreme Programming (XP) Formulated in 1999 by Kent Beck, Ward Cunningham and Ron Jeffries Agile software development methodology.

EXtreme Programming and Open Source engineering paradigm A comparison

Agile. Processes Waterfall Traditional With prototyping Sprial Agile Dynamic Systems Development Method (DSDM) Scrum Crystal eXtreme Programming (XP)

Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.

Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.

It’s Agile …. like! A Corkman’s introduction to Agile software delivery.

Engineering Practices Necessary for Scrum andrew fuqua enterprise agile coach LeadingAgile, LLC

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.

Presented By : Prima Business Solutions. Agile Software Development Process.

Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.

Embedded Systems Software Engineering

CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.

Waterfall and Agile Quality Techniques

روش‌های سريع الانتقال (چابک) توسعه نرم افزار

What do you need to know about XP?

Agile and XP Development

Agile and XP Development

Chapter 3: Agile Software Processes

Coming up: What is Agile?

Introduction to XP.

Agile software development

Presentation transcript:

Agile Software Development Practice Adoption Survey Narendra Kurapati, Venkata Sarath Chandra Manyam, and Kai Petersen Blekinge Institute of Technology Ericsson AB XP 曾毓傑

Outline Introduction Survey Design Results

Introduction Agile methodologies are often not used “out of the box” by practitioners, instead they select the practices that fit their needs best. We investigated used agile practices, combinations, degree of compliance, and how successful practitioners perceive the adoption.

Introduction (Cont.) The following survey aims at answering the following research questions: RQ1: How commonly used are individual agile practices? RQ2: Which agile practices are used together by practitioners, and how common are the combinations? RQ3: To what degree does the software industry comply to Extreme Programming (XP) and Scrum? RQ4: As how successful do the practitioners perceive the adoption of agile practices in terms of customer satisfaction and employee satisfaction?

Survey Design Find 25 agile practices used in global software development Send survey out to 600 practitioners, and post survey on LinkedIn, Yahoo, and Google groups Survey structure Introduction: Shortly explain the purpose Demographics: Ask information about organization Agile Practice Adoption: Select agile practices that they use in their project Agile Practice Adoption: Select agile practices that they use in their organization Employee Satisfaction and Customer Satisfaction Contact Details

Agile Practices Selected 1. Office Structure 2. Pair Programming 3. Planning Game/On-Site Customer 4. Tracking Progress Hour Week 6. Refactoring 7. Retrospective 8. Short/Small Release 9. Simple Design 10. Sprint/Iteration 11. Sprint Planning Meeting 12. Sprint Review Meeting 13. Stand-ups 14. Stories/Features 15. Team Work 16. Test-Driven Development 17. Testing 18. Coding Standards 19. Collective Ownership 20. Communication 21. Configuration and Change Management 22. Continuous Integration 23. Documentation 24. Informative Workshops 25. Metaphors

Results: Response Type

Results: RQ1 in Project Level

Results: RQ1 in Organizational Level

Results: RQ2 in Project Level

Results: RQ2 in Organizational Level

Results: RQ3

Results: RQ4 Employee Satisfaction

Results: RQ4 Customer Satisfaction