| |
|
|
|
|
|
|
|
|
1. |
Record Nr. |
UNINA9910811012703321 |
|
|
Autore |
Opelt Andreas <1978-> |
|
|
Titolo |
Agile contracts : creating and managing successful projects with Scrum / / Andreas Opelt ... [et al.] |
|
|
|
|
|
|
|
Pubbl/distr/stampa |
|
|
Hoboken, N.J., : Wiley, 2013 |
|
|
|
|
|
|
|
ISBN |
|
1-118-64006-3 |
1-118-64012-8 |
|
|
|
|
|
|
|
|
Edizione |
[1st ed.] |
|
|
|
|
|
Descrizione fisica |
|
1 online resource (302 p.) |
|
|
|
|
|
|
Collana |
|
Wiley series in systems engineering and management |
|
|
|
|
|
|
Altri autori (Persone) |
|
|
|
|
|
|
Disciplina |
|
|
|
|
|
|
Soggetti |
|
Agile software development |
Scrum (Computer software development) |
Computer contracts |
|
|
|
|
|
|
|
|
Lingua di pubblicazione |
|
|
|
|
|
|
Formato |
Materiale a stampa |
|
|
|
|
|
Livello bibliografico |
Monografia |
|
|
|
|
|
Note generali |
|
Description based upon print version of record. |
|
|
|
|
|
|
Nota di bibliografia |
|
Includes bibliographical references and index. |
|
|
|
|
|
|
Nota di contenuto |
|
Cover; Praise for Agile Contracts; Title page; Copyright page; Contents; Preface; Acknowledgments; 1: Agility: What Is That?; 1.1 The Agile Manifesto of 2001; 1.2 Agile Development Based on Scrum; 1.2.1 The Principles of Organization; 1.2.2 The Process Model; 1.2.3 Estimation in Scrum; 1.3 Agility from the Perspective of Procurement; 1.4 Agility from the Perspective of the Software Provider; 1.5 The 12 Principles of Agile Software Development; 1.6 Summary; 2: The Missing Piece of the Puzzle; 2.1 The Problems with Traditional Fixed-Price Contracts |
2.2 The Problems with Time and Materials Contracts2.3 Something New: The Agile Fixed-Price Contract; 2.4 Summary; 3: What Is an Agile Fixed-Price Contract?; 3.1 Existing Approaches; 3.2 The Agile Fixed-Price Contract; 3.2.1 How Is an Agile Fixed-Price Contract Set Up?; 3.3 Summary; 4: Sample of an Agile Fixed-Price Contract; Preamble; 1 Definitions and Clarifications of Terms; 2 Contract Scope and Hierarchy of Documents; 3 Usage Rights; 4 Transparency and "Open Books"; 5 Acceptance; 6 Obligation of Both Parties to Co-Operate; 7 Client's Obligations |
8 Escalation to the Steering Board and the Independent Experts9 Project Period; 10 Warranty, Compensation, and Indemnification; 11 Limitation of Liability; 12 Contractor's Compensation; 13 Force Majeure; 14 Secrecy; 15 Severability Clause; 16 Place of Performance, Jurisdiction, |
|
|
|
|
|
|
|
|
|
|
|
and Applicable Law; Appendix A: Commercial Agreements; Prices; Commercial Approach to the Project; Payment Milestones; Appendix B: Technical Scope and Process; Requirements: Backlog and Vision; Process for Development and Approval; Changes to the Contract (Exchange for Free); Deliverables and Services |
Mechanism to Calculate Costs of Future User StoriesAppendix C: 12 Principles of Cooperation; Appendix D: Quality Standards-Definition of Done; 5: Tendering Based on an Agile Fixed-Price Contract; 5.1 Appropriate Tender Content for an Agile Fixed-Price Contract; 5.2 Requirements for Tendering and Selection; 5.2.1 Competition; 5.2.2 Comparability and Transparency; 5.3 Tendering Steps with a Focus on Agile Fixed Price; 5.3.1 Internal Goal Setting and Coordination; 5.3.2 Preparation for the Invitation to Tender; 5.3.3 Tender; 5.3.4 Awarding of the Tender; 5.3.5 Price Optimization Options |
5.3.6 Project and Contract Management5.3.7 Effort Inherent in the Tendering Process; 5.4 Summary; 6: Special Requirements for the Legal Framework of an Agile Fixed-Price Contract; 6.1 Adaptable system for scope; 6.2 Warranty and Damages; 6.3 Schedule and Milestones; 6.4 Path of Escalation; 6.5 Obligations; 6.6 Summary; 7: Guideline for the Negotiation of an Agile Fixed-Price Contract; 7.1 Objectives of the Client; 7.2 Objectives of the Contractor; 7.3 Objectives and Bonus Payouts of the People Involved; 7.4 Strategy for the Project and the Negotiation; 7.5 Tactics for the Negotiation |
7.6 Price Determination |
|
|
|
|
|
|
Sommario/riassunto |
|
A methodologically sophisticated, comprehensive approach to applying the Agile fixed-price contract to IT projects while maximizing customer and supplier relationships ""Interesting and necessary for IT managers and IT lawyers.""-Walter J. Jaburek, Dipl.-Ing., Dr. iur., Dr. techn. Approximately 50 percent of software developers use Scrum, an iterative and incremental development method for managing software projects and product or application development, in their work. The benefit of Scrum and other Agile methods is that they can address shifts in a large project |
|
|
|
|
|
|
|
| |