Agile: An Executive Guide
Agile: An Executive Guide: Real results from IT budgets
JAMIE LYNN COOKE
Copyright Date: 2011
Published by: IT Governance Publishing
Pages: 94
https://www.jstor.org/stable/j.ctt5hh7pb
Search for reviews of this book
Book Info
Agile: An Executive Guide
Book Description:

Agile: An Executive Guide describes Agile methodologies in clear business language specifically written for business professionals. It will help you make realistic business-driven decisions on whether Agile methodologies are appropriate for your organisation; whether you are looking to consolidate your IT overheads, to provide better software solutions to your clients, or to have more control over your IT expenditures. This guide provides practical, proven ways to introduce, incorporate and leverage Agile methodologies to maximise your business returns.

eISBN: 978-1-84928-190-4
Subjects: Management & Organizational Behavior, Technology
You do not have access to this book on JSTOR. Try logging in through your institution for access.
Log in to your personal account or through your institution.
Table of Contents
Export Selected Citations Export to NoodleTools Export to RefWorks Export to EasyBib Export a RIS file (For EndNote, ProCite, Reference Manager, Zotero, Mendeley...) Export a Text file (For BibTex)
Select / Unselect all
  1. Front Matter
    Front Matter (pp. 1-4)
  2. DEDICATION
    DEDICATION (pp. 5-5)
  3. FOREWORD
    FOREWORD (pp. 6-6)
    Jonathan Gray

    Over the past 20 years, Agile methodologies have enabled IT projects to deliver unprecedented levels of business value to organisations worldwide. Some of these benefits can be obvious from the first time that these methodologies are used in an organisation: higher quality outputs, more relevant software solutions, greater levels of user satisfaction, and tighter control of ongoing IT expenditure.

    What may be less evident, however, are the compounded benefits that Agile methodologies can bring to organisations in the longer term: most notably, the establishment of an organisational culture that cultivates quality, inspires greater levels of employee motivation, and encourages staff...

  4. PREFACE
    PREFACE (pp. 7-9)
  5. ABOUT THE AUTHOR
    ABOUT THE AUTHOR (pp. 10-11)
  6. ACKNOWLEDGEMENTS
    ACKNOWLEDGEMENTS (pp. 12-13)
  7. Table of Contents
    Table of Contents (pp. 14-14)
  8. CHAPTER 1: AN EXECUTIVE BRIEF ON AGILE
    CHAPTER 1: AN EXECUTIVE BRIEF ON AGILE (pp. 15-41)

    ‘Agile’ is a collective term for methodologies (and practices) that have emerged over the past two decades to increase the relevance, flexibility and business value of software solutions. These methodologies are specifically intended to address the problems that have historically plagued software development activities in the IT industry, including budget overruns, missed deadlines, low quality outputs, and dissatisfied users.

    Although there are a broad range of Agile methodologies in the IT industry – from software development and project delivery approaches to strategies for software maintenance – all of these methodologies share the same basic objectives:

    replace large up-front investment in...

  9. CHAPTER 2: WHAT CAN AGILE DO FOR MY ORGANISATION?
    CHAPTER 2: WHAT CAN AGILE DO FOR MY ORGANISATION? (pp. 42-58)

    Agile is not the answer for every organisation. Dynamic organisations and organisations with unsustainable IT overheads are likely to receive a much greater ROI from implementing Agile methodologies than organisations that are not facing these challenges.

    Agile methodologies are primarily intended to manage the risk ofchangein software requirements, including the need to incorporate information that emerges during the development process. Accordingly, Agile is ideally suited for situations where the outcomes are dependent onvariable factors, such as resource availability, customer preferences and market fluctuation. It allows organisations to manage these unforeseen circumstances by expecting – and embracing –...

  10. CHAPTER 3: FIVE STEPS TO AGILE SUCCESS
    CHAPTER 3: FIVE STEPS TO AGILE SUCCESS (pp. 59-85)

    Although it might be tempting for you to want to ‘dive right in’ and start using an Agile methodology (e.g. Scrum) to salvage your struggling software projects, it is valuable for you to step back for a moment and consider the specific needs – and constraints – of your organisation.

    Decidingwhere to beginusing Agile methodologies in your organisation is as important as deciding which methodology you will use.

    Is your objective to do a ‘safe’ trial of Agile before committing to its broader use across the organisation? If so, you may want to select a self-contained new software...

  11. MORE INFORMATION ON AGILE
    MORE INFORMATION ON AGILE (pp. 86-91)
  12. ITG RESOURCES
    ITG RESOURCES (pp. 92-94)