DOCSLIB.ORG

Xp Project Management

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Xp Project Management University of Montana ScholarWorks at University of Montana Graduate Student Theses, Dissertations, & Professional Papers Graduate School 2007 XP PROJECT MANAGEMENT Craig William Macholz The University of Montana Follow this and additional works at: https://scholarworks.umt.edu/etd Let us know how access to this document benefits ou.y Recommended Citation Macholz, Craig William, "XP PROJECT MANAGEMENT" (2007). Graduate Student Theses, Dissertations, & Professional Papers. 1201. https://scholarworks.umt.edu/etd/1201 This Thesis is brought to you for free and open access by the Graduate School at ScholarWorks at University of Montana. It has been accepted for inclusion in Graduate Student Theses, Dissertations, & Professional Papers by an authorized administrator of ScholarWorks at University of Montana. For more information, please contact [email protected]. XP PROJECT MANAGEMENT By Craig William Macholz BS in Business Administration, The University of Montana, Missoula, MT, 1997 Thesis presented in partial fulfillment of the requirements for the degree of Master of Science in Computer Science The University of Montana Missoula, MT Autumn 2007 Approved by: Dr. David A. Strobel, Dean Graduate School Dr. Joel Henry Computer Science Dr. Yolanda Reimer Computer Science Dr. Shawn Clouse Business Administration i Macholz, Craig, M.S., December 2007 Computer Science Extreme Programming Project Management Chairperson: Dr. Joel Henry Extreme programming project management examines software development theory, the extreme programming process, and the essentials of standard project management as applied to software projects. The goal of this thesis is to integrate standard software project management practices, where possible, into the extreme programming process. Thus creating a management framework for extreme programming project management that gives the extreme programming managers the management activities and tools to utilize the extreme programming process within a wider range of commercial computing organizations, relationships, and development projects. The author speculates that the lack of organizational adoption and mainstream integration of the extreme programming process is connected to the lack of standard project management structure that allows for greater control of scheduling, cost, and quality. This paper will create a basic framework that will be used to improve the extreme programming process and identify its shortcomings. ii ACKNOWLEGEMENTS Thank you to Joel Henry, Ph.D., Shawn Clouse, Ph.D., and Yolanda Reimer, Ph.D for their valued input and support. Special thanks to my wife Lee, daughter Kaylee and my parents, Jim and Sue Macholz. iii TABLE OF CONTENTS LIST OF TABLES .......................................................................................VII LIST OF ILLUSTRATIONS ....................................................................................VII CHAPTER 1 – INTRODUCTION ...............................................................................1 1.1– PROBLEM STATEMENT...............................................................................................................................1 1.2 – APPROACH/METHODS...............................................................................................................................2 1.3 – SOFTWARE PROCESS BACKGROUND ........................................................................................................3 CHAPTER 2 – OVERVIEW OF EXTREME PROGRAMMING .............................7 2.1 – THE PURPOSE OF XP .................................................................................................................................8 2.2 – RIGHTS WITHIN XP...................................................................................................................................9 2.3 – XP CORE VALUES...................................................................................................................................11 2.4 – XP CORE PRACTICES ..............................................................................................................................12 2.5 – THE PLANNING GAME.............................................................................................................................13 2.5.1 – User Stories ....................................................................................................................................13 2.5.2 – Story Estimation .............................................................................................................................16 2.5.3 – Release Planning............................................................................................................................18 2.5.4 – Iteration Planning ..........................................................................................................................20 2.6 – SMALL RELEASES....................................................................................................................................21 2.7 – SYSTEM METAPHOR................................................................................................................................21 2.8 – SIMPLE DESIGN .......................................................................................................................................22 2.9 – TESTING...................................................................................................................................................23 2.9.1 – Unit Tests........................................................................................................................................23 2.9.2 – Acceptance Tests ............................................................................................................................25 2.10 – REFACTORING .......................................................................................................................................26 2.11 – PAIR PROGRAMMING ............................................................................................................................27 2.12 – COLLECTIVE OWNERSHIP .....................................................................................................................28 2.13 – CONTINUOUS INTEGRATION .................................................................................................................29 2.13.1 – Releasing Changes .......................................................................................................................29 2.13.2 – Possible Problems and Fixes.......................................................................................................30 2.13.3 – Slow Merges .................................................................................................................................30 2.13.4 – Lost Changes ................................................................................................................................31 2.14 – 40-HOUR WORKWEEK ..........................................................................................................................31 2.15 – ON-SITE CLIENT....................................................................................................................................31 2.16 – CODING STANDARDS ............................................................................................................................32 2.17 – XP PRACTICES SUMMARY....................................................................................................................33 2.18 – ROLES OF THE XP TEAM MEMBERS.....................................................................................................34 2.18.1 – Programmer..................................................................................................................................34 2.18.2 – Customer.......................................................................................................................................35 2.18.3 – Tester ............................................................................................................................................36 2.18.4 – Tracker..........................................................................................................................................36 2.18.5 – Coach............................................................................................................................................36 2.18.6 – Consultant.....................................................................................................................................37 2.18.7 – Manager........................................................................................................................................37 2.19 – XP MANAGEMENT STRATEGY .............................................................................................................39 2.19.1 – Metrics ..........................................................................................................................................40 iv 2.19.2 – Coaching.......................................................................................................................................42 2.19.3 – Intervention...................................................................................................................................42 2.20 – FACILITIES.............................................................................................................................................43
Load more

Recommended publications
  • Information Technology and Software Development
    Course Title: Information Technology and Software Development NATIONAL OPEN UNIVERSITY OF NIGERIA SCHOOL OF SCIENCE AND TECHNOLOGY COURSE CODE: CIT 703 COURSE TITLE: Information Technology and Software Development National Open University of Nigeria, Victoria Island, Lagos Page 1 Course Title: Information Technology and Software Development Course Code Course Title Information Technology and Software Development Course Developer/Writer Eze, Festus Chux Department of Computer Science Ebonyi State University Abakaliki Course Editor Programme Leader Course Coordinator National Open University of Nigeria, Victoria Island, Lagos Page 2 Course Title: Information Technology and Software Development Introduction Information Technology and Software Development is a three credit load course for all the students offering Post Graduate Diploma (PGD) in Computer Science, Information Technology and other allied courses. Software Development is a major branch in computing and information Technology. A software development professional oversees the processes of software development, the management of software development project, the maintenance of the installed software in an organisation. For sometime the field has been dominated with what is the definitive process of software development. Furthermore there has been the running battle between professionals and managers on who should control a software development project. There is an attempt to classify it as any other project that an organisation handles hence anybody could manage it. Whereas others see it as a highly professional issue that requires high precision in design, management and implementation. However, software development is all involving. It involves the user (client) whose interest is paramount. The developing organisation and her professionals ( team)are of great importance. Therefore a successful exercise can only take place when all these variegated interests are harmonised.
    [Show full text]
  • The Great Methodologies Debate: Part 1
    ACCESS TO THE EXPERTS The Journal of Information Technology Management December 2001 Vol. 14, No. 12 The Great Methodologies Debate: Part 1 Resolved “Today, a new debate rages: agile software Traditional methodologists development versus rigorous software are a bunch of process- development.” dependent stick-in-the-muds who’d rather produce flawless Jim Highsmith, Guest Editor documentation than a working system that meets business needs. Opening Statement Jim Highsmith 2 Rebuttal Lightweight, er, “agile” Agile Can Scale: Inventing and Reinventing methodologists are a bunch of SCRUM in Five Companies glorified hackers who are going to be in for a heck of a surprise Jeff Sutherland 5 when they try to scale up their “toys” into enterprise-level software. Agile Versus Traditional: Make Love, Not War! Robert L. Glass 12 Business Intelligence Methodologies: Agile with Rigor? Larissa T. Moss 19 Agility with the RUP Philippe Kruchten 27 Extreme Requirements Engineering Larry Wagner 34 Exclusion, Assumptions, and Misinterpretation: Foes of Collaboration Lou Russell 39 Opening Statement by Jim Highsmith In the early 1980s, I participated in rigorous software development. others be able to understand the one round of methodology debate. Agile approaches (Extreme similarities and differences and be Structured analysis and design Programming, Crystal Methods, able to apply the right mix to their champions such as Tom DeMarco, Lean Development, Feature-Driven own organization. Both the SEI and Ed Yourdon, and Tim Lister were Development, Adaptive Software Rational have made wonderful on one side of the debate, while Development, SCRUM, and contributions to software develop- data-driven design aficionados like Dynamic Systems Development ment, but it is important to Ken Orr, Jean-Dominique Warnier, Methodology) populate one camp.
    [Show full text]
  • Empirical Studies of Agile Software Development: a Systematic Review
    Available online at www.sciencedirect.com Information and Software Technology 50 (2008) 833–859 www.elsevier.com/locate/infsof Empirical studies of agile software development: A systematic review Tore Dyba˚ *, Torgeir Dingsøyr SINTEF ICT, S.P. Andersensv. 15B, NO-7465 Trondheim, Norway Received 22 October 2007; received in revised form 22 January 2008; accepted 24 January 2008 Available online 2 February 2008 Abstract Agile software development represents a major departure from traditional, plan-based approaches to software engineering. A system- atic review of empirical studies of agile software development up to and including 2005 was conducted. The search strategy identified 1996 studies, of which 36 were identified as empirical studies. The studies were grouped into four themes: introduction and adoption, human and social factors, perceptions on agile methods, and comparative studies. The review investigates what is currently known about the benefits and limitations of, and the strength of evidence for, agile methods. Implications for research and practice are presented. The main implication for research is a need for more and better empirical studies of agile software development within a common research agenda. For the industrial readership, the review provides a map of findings, according to topic, that can be compared for relevance to their own settings and situations. Ó 2008 Elsevier B.V. All rights reserved. Keywords: Empirical software engineering; Evidence-based software engineering; Systematic review; Research synthesis; Agile software development; XP; Extreme programming; Scrum Contents 1. Introduction . 834 2. Background – agile software development . 834 2.1. The field of agile software development. 834 2.2. Summary of previous reviews .
    [Show full text]
  • Multi-Factor Analysis of Pair Programming Based on PSP
    I S S N 2 2 7 7 - 3 0 6 1 V o l u m e 1 5 N u m b e r 0 4 INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY Multi-factor analysis of pair programming based on PSP methodology Nabiollah Bayatmoghadam1 (M.S), Ashkan Sami (Ph.D.)2 1Department of Computer Science, Engineering, Shiraz University Email: [email protected] 2Department of Computer Science, Engineering, Shiraz University ABSTRACT In regard with designing software, users play key role. In order to design software, it is necessary to observe standard principles of designation, using templates and using modern methods. Over the decades, using development methods, XP and one of the XP methodologies of paired programming used to design software. These methods have been designed for purpose of enhancing quality of product and rapidresponse to need of market and customer and overcoming weaknesses of traditional methods based on long-term programming and waterfall method. Therefore, every programmer and developer can pass a series of processes for constructing computer software. The processes can be changed daily and efficient processes maynot be effective and useful; although they can be considered as process. The main objective of the present study is multi-factor analysis of pair programming based on PSP methodology. Practical and analytical methodand two PSP methods have been applied for investigations. Key words: software engineering, XP, pair programming, PSP methodology, multi-factor analysis INTRODUCTION In designing software, users play key role. In order to design software, it is necessary to observe standard principles of designation and using templates and using modern technologies.
    [Show full text]
  • Evaluating Effectiveness of Pair Programming As a Teaching Tool in Programming Courses
    Information Systems Education Journal (ISEDJ) 12 (6) ISSN: 1545-679X November 2014 Evaluating Effectiveness of Pair Programming as a Teaching Tool in Programming Courses Silvana Faja [email protected] School of Accountancy and Computer Information Systems, University of Central Missouri, Warrensburg, Missouri, 64093, USA Abstract This study investigates the effectiveness of pair programming on student learning and satisfaction in introductory programming courses. Pair programming, used in the industry as a practice of an agile development method, can be adopted in classroom settings to encourage peer learning, increase students’ social skills, and enhance student achievement. This study explored students’ perceptions on effectiveness of pair programming and the influence of student’s level of experience with this activity and perceived partner involvement on effectiveness outcomes. Findings suggest that the more students are involved in this activity, the more they enjoy it and the more they learn by collaborating with their partners. When comparing different effectiveness measures, their perceived learning, quality of work, and enjoyment during pair programming was found to be at a higher level than increased productivity outcome. Keywords: Pair Programming, Teamwork, Collaborative Learning, Programming Course. 1. INTRODUCTION information systems courses. It discusses what was learned about the impact of this type of Software development is typically a process that collaborative activity on students’ attitudes and requires the coordinated efforts of the members learning. The following section provides a of one or more teams. As such, it is important review of existing research on pair that computer programming courses provide programming, collaborative learning and students not only with technical knowledge, but research questions and hypotheses.
    [Show full text]
  • The Role of Customers in Extreme Programming Projects
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by ResearchArchive at Victoria University of Wellington THE ROLE OF CUSTOMERS IN EXTREME PROGRAMMING PROJECTS By Angela Michelle Martin A thesis submitted to the Victoria University of Wellington in fulfilment of the requirements for the degree of Doctor of Philosophy In Computer Science Victoria University of Wellington 2009i The Role of Customers in Extreme Programming Projects ABSTRACT eXtreme programming (XP) is one of a new breed of methods, collectively known as the agile methods, that are challenging conventional wisdom regarding systems development processes and practices. Practitioners specifically designed the agile methods to meet the business problems and challenges we face building software today. As such, these methods are receiving significant attention in practitioner literature. In order to operate effectively in the world of vague and changing requirements, XP moves the emphasis away from document-centric processes into practices that enable people. The Customer is the primary organisational facing role in eXtreme Programming (XP). The Customer's explicit responsibilities are to drive the project, providing project requirements (user stories) and quality control (acceptance testing). Unfortunately the customer must also shoulder a number of implicit responsibilities including liaison with external project stakeholders, especially project funders, clients, and end users, while maintaining the trust of both the development team and the wider business. This thesis presents a grounded theory of XP software development requirements elicitation, communication, and acceptance, which was guided by three major research questions. What is the experience of being an XP Customer? We found that teams agree that the on-site customer practice is a drastic improvement to the traditional document-centric approaches.
    [Show full text]
  • Enhancing Learnability of Pair Programming Practice When Introducing Novices
    MASARYKOVA UNIVERZITA FAKULTA INFORMATIKY Enhancing Learnability of Pair Programming Practice when Introducing Novices DIPLOMOVÁ PRÁCE Pavel Januš Brno, jaro 2014 Declaration I declare that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Advisor: Bruno Rossi, PhD. i Acknowledgement I would like to express my gratitude to my supervisor Bruno Rossi for leading me through the creation of my diploma thesis. I am grateful to him for stimulating discus- sions about the content of the thesis and supporting developing of my own ideas. I also want to appreciate his provided time, knowledge, valuable information and his patience and willingness. I express special thanks to my parents for their understanding, and my girlfriend for her support. ii Abstract The current thesis focuses on understanding the mechanisms that lead novice develop- ers to better learn the Pair Programming (PP) practice, one of the pillars of Agile Metho- dologies. The main aim is to provide theoretical-grounded suggestions that could help to improve the process by which novices are introduced to PP and start mastering it. To contextualize PP, we review the emergence of Agile development methodology com- pared to more heavy-weight methodologies and we evaluate the importance of PP as one of the key practices of Extreme Programing (XP). We then delve into empirical stu- dies that investigate the efficacy of PP in software development and into the identifica- tion of the state of the art in terms of the introduction of PP to novices.
    [Show full text]
  • Software Testing: a Changing Career
    Software Testing: A Changing Career Sean Cunningham1, Jemil Gambo1, Aidan Lawless1, Declan Moore1, Murat Yilmaz2, Paul M. Clarke 1,3 [0000-0002-4487-627X], Rory V. O’Connor1,3 [0000-0001-9253-0313] 1 School of Computing, Dublin City University, Ireland {sean.cunningham29,jemil.gambo2,aidan.lawless8, declan.moore39}@mail.dcu.ie 2 Department of Computer Engineering, Cankaya University, Turkey [email protected] 3 Lero, the Irish Software Engineering Research Center {rory.oconnor,paul.m.clarke}@dcu.ie The software tester is an imperative component to quality software development. Their role has transformed over the last half a century and volumes of work have documented various approaches, methods, and skillsets to be used in that time. Software projects have gone from using monolithic architectures and heavy- weight methodologies, to service-oriented and lightweight. Testing has trans- formed from a sequential step performed by dedicated testers to a continuous activity carried out by various development professionals. Technological ad- vancements have pushed automation into routine test tasks permitting a change of focus for the tester. Management styles and methodologies have pushed de- velopment to be agile and lean, towards continuous integration and frequent re- lease. Regardless of these many important changes, the software tester’s role re- mains the verification and validation of software code. Keywords: software quality improvement, test drive development, continuous development, software development lifecycle 1 Introduction It is well documented that software development is a complex socio-technical activity [42], the process for which needs to be vigilantly maintained and evolved [43]. We furthermore find that roles within software development can have varying names [44], and that the very terminology adopted is perhaps the source of some fusion [45] [46].
    [Show full text]
  • Incorporating Aspects Into the Software Development Process in Context of Aspect- Oriented Programming Mark Alan Basch University of North Florida
    UNF Digital Commons UNF Graduate Theses and Dissertations Student Scholarship 2002 Incorporating Aspects into the Software Development Process in Context of Aspect- Oriented Programming Mark Alan Basch University of North Florida Suggested Citation Basch, Mark Alan, "Incorporating Aspects into the Software Development Process in Context of Aspect-Oriented Programming" (2002). UNF Graduate Theses and Dissertations. 112. https://digitalcommons.unf.edu/etd/112 This Master's Thesis is brought to you for free and open access by the Student Scholarship at UNF Digital Commons. It has been accepted for inclusion in UNF Graduate Theses and Dissertations by an authorized administrator of UNF Digital Commons. For more information, please contact Digital Projects. © 2002 All Rights Reserved INCORPORATING ASPECTS INTO THE SOFTWARE DEVELOPMENT PROCESS IN THE CONTEXT OF ASPECT -ORIENTED PROGRAMMING by Mark Alan Basch A thesis submitted to the Department of Computer and Information Sciences in partial fulfillment of the requirements for the degree of Master of Science in Computer and Information Sciences UNIVERSITY OF NORTH FLORIDA DEPARTMENT OF COMPUTER AND INFORMATION SCIENCES December 2002 ACKNOWLEDGEMENT I wish to thank my thesis adviser, Dr. Arturo 1. Sanchez, for his assistance and patience in guiding me through the thesis process. 11 The thesis "Incorporating Aspects into the Software Development Process in the Context of Aspect-Oriented Programming" submitted by Mark Alan Basch in partial fulfillment of the requirements for the degree of Master of Science in Computer and Information Science has been Appro d b the ¥eSiS mmittee Date Signature Deleted c ez Thesis Adviser and Committee Chairperson Signature Deleted Robert F. Roggio Signature Deleted Neal S.
    [Show full text]
  • On-Demand Collaboration in Programming
    On-Demand Collaboration in Programming YAN CHEN, University of Michigan, Ann Arbor JASMINE JONES, Berea College, Berea STEVE ONEY, University of Michigan, Ann Arbor Many teams have shifted to online remote collaboration as a result of COVID-19, from professional development teams to programming classes to computing-related workspaces (e.g., makerspaces). This paper explores on-demand remote help seeking in programming, a type of collaboration that occurs when developers seek online support for their tasks as needed, and argues that a key challenge in scaling remote on-demand collaboration in programming is to facilitate effective context capturing and workforce coordination. Traditionally, this collaboration happens within teams and organizations where people are familiar with the context of the tasks. Recently, this collaboration has become ubiquitous due to the success of paid online crowdsourcing marketplaces (e.g., Upwork) and Q&A sites (e.g., Stack Overflow). We discuss prior work on on-demand collaboration in programming, analyze how the ideacanbe tested in physical computing as well, and examine existing and new challenges that should be further explored. CCS Concepts: • Computer systems organization ! Embedded systems; Redundancy; Robotics; • Networks ! Network relia- bility. Additional Key Words and Phrases: on-demand support; programming collaboration; crowdsourcing ACM Reference Format: Yan Chen, Jasmine Jones, and Steve Oney. 2018. On-Demand Collaboration in Programming. In New Future of Work ’20: ACM Symposium on Neural Gaze Detection, June 03–05, 2018, Woodstock, NY. ACM, New York, NY, USA,4 pages. https://doi.org/10.1145/1122445.1122456 1 INTRODUCTION Technology companies, schools, bootcamps, and makerspaces have shifted to prolonged online work as a result of COVID-19.
    [Show full text]
  • Certificate: Computer Programming
    Certificates and Degrees Certificate: Computer Programming Certificate Description: The computer programming certificate provides students with an understanding of how to design and develop programs in a variety of computer languages, including Javascript, Python, PHP, and Java. Course Code Course Name 15 Credits CSPC 101 Introduction to Programming 2 Credits CIT 160 Introduction to Programming 3 Credits CS 241 Survey Object-Oriented Programming/Data Structures 4 Credits CS 213 Web Engineering 3 Credits CS 246 Software Design and Development 3 Credits Course Descriptions: CSPC 101 (2 credits) – Introduction to Programming This course introduces computer programming intended for people with no programming experience. This course covers the basics of programming in Python, including elementary data types (numeric types, strings, lists, dictionaries and files), control flow, functions, objects, methods, fields, and mutability. CIT 160 (3 credits) – Introduction to Programming This course is an introduction to the basic concepts of computers and information technology. Students will learn the basics of computer hardware and the binary and hexadecimal number systems, design algorithms to solve simple computing problems, and write computer programs using Boolean logic, control structures, and functions. CS 241 (4 credits) – Survey Object-Oriented Programming/Data Structures This course introduces object-oriented programming and common data structures. CS 213 (3 credits) – Web Engineering Internet and web basics, web fundamentals, web browsers,
    [Show full text]
  • Architecting the Cloud, Part of the on Cloud Podcast
    Architecting the Cloud May 2020 Architecting the Cloud, part of the On Cloud Podcast Mike Kavis, Managing Director, Deloitte Consulting LLP Title: Software testing in the age of cloud—new ideas and opportunities Description: Testing has always been a critical component of good software development practice. However, it’s often short-shrifted or siloed. As a result, app performance can suffer. In this episode of the podcast, Mike Kavis and guest, mabl’s Lisa Crispin, discuss the evolution of testing and how new development ideologies like DevOps have shed light on the importance of testing. Lisa also talks about how the cloud has transformed software testing by making it faster and automating much of the process, so that testers can focus on crucial human-centric testing such as security and accessibility testing. Lisa also touches on how cloud-native apps changes the testing process and gives her advice on how companies can learn more about testing and use that knowledge to improve their software delivery process. Duration: 00:23:48 Operator: This podcast is produced by Deloitte. The views and opinions expressed by podcast speakers and guests are solely their own and do not reflect the opinions of Deloitte. This podcast provides general information only and is not intended to constitute advice or services of any kind. For additional information about Deloitte, go to Deloitte.com/About. Welcome to Architecting the Cloud, part of the On Cloud Podcast, where we get real about Cloud Technology what works, what doesn't and why. Now here is your host Mike Kavis. Mike Kavis: Hey, everyone.
    [Show full text]