0% found this document useful (0 votes)
16 views92 pages

And Kanban Lean Implementation An Action Guide For Business and It Leaders 4740016

Uploaded by

xjuuixdqx0989
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
16 views92 pages

And Kanban Lean Implementation An Action Guide For Business and It Leaders 4740016

Uploaded by

xjuuixdqx0989
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

(Ebook) Business-Driven IT-Wide Agile (scrum) and Kanban

(Lean) Implementation: An Action Guide for Business and


IT Leaders by Andrew Thu Pham, David Khoi Pham ISBN
9781466557482, 1466557486 Pdf Download

https://ebooknice.com/product/business-driven-it-wide-agile-scrum-
and-kanban-lean-implementation-an-action-guide-for-business-and-it-
leaders-4740016

★★★★★
4.7 out of 5.0 (27 reviews )

DOWNLOAD PDF

ebooknice.com
(Ebook) Business-Driven IT-Wide Agile (scrum) and Kanban
(Lean) Implementation: An Action Guide for Business and IT
Leaders by Andrew Thu Pham, David Khoi Pham ISBN
9781466557482, 1466557486 Pdf Download

EBOOK

Available Formats

■ PDF eBook Study Guide Ebook

EXCLUSIVE 2025 EDUCATIONAL COLLECTION - LIMITED TIME

INSTANT DOWNLOAD VIEW LIBRARY


We have selected some products that you may be interested in
Click the link to download now or visit ebooknice.com
for more options!.

(Ebook) Business-Driven IT-Wide Agile (Scrum) and Kanban (Lean)


Implementation: An Action Guide for Business and IT Leaders by
Andrew Thu Pham (Author); David Khoi Pham (Author) ISBN
9780429253959, 9781138423237, 9781466557482, 9781466557499,
9781466578555, 9781466578562, 0429253958, 1138423238, 1466557486
https://ebooknice.com/product/business-driven-it-wide-agile-scrum-and-
kanban-lean-implementation-an-action-guide-for-business-and-it-
leaders-12052796

(Ebook) From Business Strategy to Information Technology


Roadmap: A Practical Guide for Executives and Board Members by
Tiffany Pham, David K. Pham, Andrew Pham ISBN 9781466585027,
1466585021
https://ebooknice.com/product/from-business-strategy-to-information-
technology-roadmap-a-practical-guide-for-executives-and-board-
members-4739046

(Ebook) From Business Strategy to Information Technology


Roadmap: A Practical Guide for Executives and Board Members by
Tiffany Pham; David K. Pham; Andrew T. Pham ISBN 9781466585027,
9781466585034, 1466585021, 146658503X
https://ebooknice.com/product/from-business-strategy-to-information-
technology-roadmap-a-practical-guide-for-executives-and-board-
members-7162258

(Ebook) Scrum in Action by Andrew (Andrew Pham) Pham, Phuong-Van


Pham ISBN 143545913X, 1435459148

https://ebooknice.com/product/scrum-in-action-2209994
(Ebook) Vagabond, Vol. 29 (29) by Inoue, Takehiko ISBN
9781421531489, 1421531488

https://ebooknice.com/product/vagabond-vol-29-29-37511002

(Ebook) Process-Driven SOA: Patterns for Aligning Business and


IT by Carsten Hentrich, Uwe Zdun ISBN 9781439889299, 1439889295

https://ebooknice.com/product/process-driven-soa-patterns-for-aligning-
business-and-it-4398102

(Ebook) Biota Grow 2C gather 2C cook by Loucas, Jason; Viles,


James ISBN 9781459699816, 9781743365571, 9781925268492,
1459699815, 1743365578, 1925268497

https://ebooknice.com/product/biota-grow-2c-gather-2c-cook-6661374

(Ebook) The Business-Minded CISO: How to Organize, Evangelize,


and Operate an Enterprise-wide IT Risk Management Program by
Bryan C. Kissinger ISBN 9781951527518, 1951527518

https://ebooknice.com/product/the-business-minded-ciso-how-to-organize-
evangelize-and-operate-an-enterprise-wide-it-risk-management-
program-11035188

(Ebook) 29, Single and Nigerian by Naijasinglegirl ISBN


9781310004216, 1310004218

https://ebooknice.com/product/29-single-and-nigerian-53599780
Business-Driven
IT-Wide Agile (Scrum)
and Kanban (Lean)
Implementation
An Action Guide for Business and IT Leaders

Andrew T. Pham and David K. Pham


Foreword by Jack Bergstrand,
Former CFO of the Coca-Cola Beverages and CIO of the Coca-Cola Company
Foreword by Adam Warner, IT Management, ESC
Business-Driven
IT-Wide Agile (Scrum)
and Kanban (Lean)
Implementation

An Action Guide for Business and IT Leaders


Business-Driven
IT-Wide Agile (Scrum)
and Kanban (Lean)
Implementation

An Action Guide for Business and IT Leaders

Andrew T. Pham and David K. Pham

Foreword by Jack Bergstrand,


Former CFO of the Coca-Cola Beverages and CIO of the Coca-Cola Company

Foreword by Adam Warner, IT Management, ESC


CRC Press
Taylor & Francis Group
6000 Broken Sound Parkway NW, Suite 300
Boca Raton, FL 33487-2742

© 2013 by Taylor & Francis Group, LLC


CRC Press is an imprint of Taylor & Francis Group, an Informa business

No claim to original U.S. Government works


Version Date: 20120726

International Standard Book Number-13: 978-1-4665-5749-9 (eBook - PDF)

This book contains information obtained from authentic and highly regarded sources. Reasonable efforts have been made to
publish reliable data and information, but the author and publisher cannot assume responsibility for the validity of all materials
or the consequences of their use. The authors and publishers have attempted to trace the copyright holders of all material repro-
duced in this publication and apologize to copyright holders if permission to publish in this form has not been obtained. If any
copyright material has not been acknowledged please write and let us know so we may rectify in any future reprint.

Except as permitted under U.S. Copyright Law, no part of this book may be reprinted, reproduced, transmitted, or utilized in any
form by any electronic, mechanical, or other means, now known or hereafter invented, including photocopying, microfilming,
and recording, or in any information storage or retrieval system, without written permission from the publishers.

For permission to photocopy or use material electronically from this work, please access www.copyright.com (http://www.copy-
right.com/) or contact the Copyright Clearance Center, Inc. (CCC), 222 Rosewood Drive, Danvers, MA 01923, 978-750-8400.
CCC is a not-for-profit organization that provides licenses and registration for a variety of users. For organizations that have been
granted a photocopy license by the CCC, a separate system of payment has been arranged.

Trademark Notice: Product or corporate names may be trademarks or registered trademarks, and are used only for identifica-
tion and explanation without intent to infringe.
Visit the Taylor & Francis Web site at
http://www.taylorandfrancis.com

and the CRC Press Web site at


http://www.crcpress.com
To Jessica, Tiffany, and Kym, with love
Contents

Foreword by Jack Bergstrand.......................................................... xiii


Foreword by Adam Warner................................................................xv
Preface: What Is This Book About?................................................. xix
Acknowledgments........................................................................... xxi
About the Authors......................................................................... xxiii

Section Iâ•…SETTING UP THE STAGE


â•⁄ 1 Ineffectiveness of IT Software Project Management
and Development: What Can We Do about It?..............................3
Why Are Command-�and-�Control and Waterfall Life Cycle
Approaches Harmful When Used Together?...............................................4
What Can We Do about It?..........................................................................6
â•⁄ 2 Executive Summary of Agile (Scrum) and Kanban (Lean)............7
So, What Is Agile?........................................................................................7
Agile Manifesto.....................................................................................7
Example of a Known Agile Process: Scrum........................................9
Agile Practices in a Nutshell..............................................................11
So, What Is Lean and What Is Kanban?....................................................12
So, What Is Lean?...............................................................................12
So, What Is Kanban?..........................................................................14
Kanban Practices in a Nutshell..........................................................22
Similarities between Agile/�Scrum and Kanban........................................22
Summary....................................................................................................24
Endnotes.....................................................................................................24

vii
viii ◾ Contents

â•⁄ 3 Why Agile Alone May Not Be Enough or the Right Solution,
and Why Implementing Agile or Kanban without Good
Business Objectives Will Normally Fail......................................27
Why Agile Alone May Not Be Enough (Preliminary Case Study #1).......27
Initial Planning...................................................................................28
Pilot Project Team..............................................................................28
Initial Project Team Training..............................................................28
On-Site Scrum Workshop...................................................................29
Second Sprint: Another Hit for the Team!.........................................30
Third Sprint: Things Started to Rumble.............................................30
Fourth Sprint: Things Became Worse and Worse.............................30
Fifth Sprint: Project Was Cancelled!...................................................30
Lessons Learned.................................................................................30
From Scrum to Kanban (Preliminary Case Study #2)...............................32
Context...............................................................................................32
Information Technology.....................................................................33
There Is Nothing They Do Not Have................................................33
Feedback from the Trenches..............................................................33
Finally the Truth Came Out...............................................................33
Kanban Came to the Rescue..............................................................34
Pitfalls of New Software Processes...........................................................34
Release and Sprint Planning..............................................................35
Scrum Ceremonies.............................................................................36
First Month..........................................................................................36
Change in Product Owner.................................................................36
Different Understanding of Agile and Scrum....................................37
Building New Expectations...............................................................37
Nice Surprise......................................................................................38
Agile Started to Rumble.....................................................................38
Back to Waterfall and Command and Control..................................39

Section IIâ•…BUSINESS GOALS–Â�DRIVEN IT-Â�WIDE SOFTWARE


DELIVERY IMPROVEMENT FRAMEWORK
â•⁄ 4 Seven-Â�Step Software Delivery Improvement Framework...........43
Description.................................................................................................43
Step 1: Identify the Business Sponsor and Her or His Needs
and Goals...........................................................................................43
Identify the Business Sponsor....................................................43
Identify Business Problems and Issues......................................44
Contents ◾ ix

Identify Business and IT Goals..................................................45


Identify Measurements...............................................................45
Step 2: Perform Environment Boundary Identification and
Assessment.........................................................................................45
Identify the Boundary................................................................46
Environment Assessment............................................................46
Findings Summary......................................................................46
Step 3: Envision Scenarios and Risks................................................46
Step 4: Detail the Chosen Action Plan..............................................47
Step 5: Implement the Chosen Action Plan.......................................47
Step 6: Inspect the Implementation’s Progress..................................47
Step 7: Adapt the Chosen Action Plan (as Needed)..........................47
Summary....................................................................................................48
â•⁄ 5 Step 1: Identify the (Business) Sponsor and Her or His
Needs and Goals.........................................................................49
Identify the (Business) Sponsor(s).............................................................49
Identify the Sponsor(s)’ Needs and Goals................................................50
Summary....................................................................................................52
â•⁄ 6 Step 2: Perform Environment Boundary Identification and
Assessment.................................................................................53
How to Identify the Environment Boundary............................................53
Assess the Identified Business and IT Environment................................54
Findings Summary.............................................................................56
Summary....................................................................................................56
â•⁄ 7 Step 3: Envision Scenarios and Risks.........................................63
From Goals to Action Items (in Bypassing the Assessment)....................63
How to Identify Risks (for Different Scenarios)........................................65
Scenario Consolidation..............................................................................68
Summary....................................................................................................69
â•⁄ 8 Step 4: Detail the Chosen Action Plan........................................71
Anatomy of a Detailed Scenario (Chosen Action Plan)............................71
Seven Characteristics of a Good Action Plan...........................................74
Summary....................................................................................................76
â•⁄ 9 Step 5: Implement the Chosen Action Plan................................77
Set Up the Implementation Structure........................................................77
Seven Characteristics of an Effective Plan Execution...............................78
Summary....................................................................................................79
x ◾ Contents

10 Step 6: Inspecting the Implementation’s Progress.....................81


Why Is Regular Progress Inspection Critical?............................................81
What to Inspect..........................................................................................81
At the Overall Plan Level...................................................................82
At the Action Item Level....................................................................82
Summary....................................................................................................83
11 Step 7: Adapt the Chosen Action Plan (as Needed)....................87
Different Types of Change.........................................................................87
Strategic Change.................................................................................87
Operational Change...........................................................................87
Examples of Adaptations...........................................................................88
Strategic Impact..................................................................................88
Operational Impact............................................................................88
Summary....................................................................................................88

Section IIIâ•…RETROSPECTIVES
12 Lessons Learned.........................................................................93

Section IVâ•…CASE STUDIES


Case Study 1: “Customized Agile Combined with Kanban”..............97
Step 1: Identify Business Sponsor and Her or His Needs and Goals......97
Step 2: Perform ATP’s Environment Boundary Identification and
Assessment...............................................................................................100
ATP Process Improvement Effort’s Boundary.................................100
Environment Assessment................................................................. 101
Findings Summary........................................................................... 101
Step 3: Envision ATP Scenarios............................................................... 111
Step 4: Develop the Detailed Action Plan for ATP................................. 112
Step 5: Execute the ATP Action Plan...................................................... 119
Step 6: Inspect ATP Execution’s Progress...............................................122
Identify and Mitigate Risks..............................................................122
Organize Effective Retrospectives and Learn from Their
Lessons.............................................................................................125
Inspect the Actual Budget to Watch Out for Variance....................125
Watch Out for Positive (and Less than Positive) Changes
Coming from the Different Dimensions..........................................126
Contents ◾ xi

Step 7: Adapt the ATP Plan......................................................................126


Change from the Action Items and the Environment Reaction
to the Action Plan.............................................................................127
Change Due to Change in Business and/�or IT Strategy.................128
Lessons Learned.......................................................................................128
Case Study 2: “(Customized) Agile and Kanban Coexistence”..........131
Step 1: Identify WTR’s Business Sponsor and Her Needs and Goals....132
Mary Beckers’s Organization...........................................................132
First Preliminary Training................................................................132
Step 2: Perform WTR Environment Boundary Identification and
Assessment...............................................................................................136
Step 3: WTR Scenarios Envisioning........................................................138
Scenarios Risk Analysis....................................................................138
Step 4: Developing the Detailed Action Plan for WTR..........................139
Step 5: Execute the WTR Action Plan.....................................................139
Step 6: Inspect Progress of the WTR Action Plan.................................. 141
Identify and Mitigate Risks.............................................................. 142
Lessons from the Pilot Project’s Retrospectives...............................146
Inspect the Actual Budget to Watch Out for Variance.................... 146
Watch Out for Positive—and Less than Positive—Changes on
the Different Dimensions................................................................. 146
Step 7: Adapt the WTR Action Plan........................................................146
Changes Coming from the Action Items and the Environment
Reaction to the Action Plan.............................................................146
Organizational..........................................................................146
Process...................................................................................... 149
Change Due to Change in Business and/�or IT Strategy................. 150
Lessons Learned....................................................................................... 150

Section Vâ•…APPENDICES
Appendix A: From the Project Management Office to the Project
Delivery Office................................................................................ 155
Modify the Traditional Project Manager’s Job Description..................... 156
Project Manager’s Traditional Job Description................................ 156
Agile/Â�Lean Project Manager’s New Job Description....................... 156
Change the Way the PMO Calculates Its Project Estimate..................... 157
Appendix B: Change Management.................................................. 159
xii ◾ Contents

Appendix C: Two Most Important Tools of a Good Software


Development Infrastructure............................................................ 161
Continuous Integration............................................................................ 161
Automated Testing................................................................................... 162
Glossary...........................................................................................163
Bibliography.................................................................................... 167
Foreword

In our globally competitive and fast-changing business world, better and


more productive projects are to the twenty-�first century what better assem-
bly lines were to the twentieth century. Unfortunately, the conventional proj-
ect management approach fails to deliver on management’s initial goals an
alarming 70% of the time. Then enter Agile (Scrum) and, more increasingly,
Kanban (Lean) with all the benefits they bring along.
Imagine how much better your software team’s work would be if you
were continually able, in some cases, to act on what team members did
yesterday, what they are going to do today, and whether or not there are
any obstacles to solve. Also, imagine how much better it would be, in other
cases, if you could help improve your software team’s work by not introduc-
ing a completely new process to the team, but instead visualized their cur-
rent process while trying to optimize it with proven approaches—Kanban,
among others—coming from the best just-Â�in-Â�time system in the world, the
Toyota Production System (TPS).
As a logical sequence to their first book, Scrum in Action: Agile Software
Project Management and Development, which is geared toward project
teams, Andrew Pham and David Pham’s new book is decidedly geared
toward business and information technology (IT) executives who would like
to know how to successfully deploy Agile (Scrum) and/�or Kanban (Lean)
on a large scale to IT in their effort to increase their teams’ software deliv-
ery capability.
As a former CFO of the Coca-�Cola Beverages and CIO of the Coca-�
Cola Company, I truly appreciate Andrew Pham and David Pham for hav-
ing developed in this book a comprehensive and easy-�to-�follow guide for
busy executives. Likewise, I also truly appreciate the fact that the authors’
approach also factors in change, communication, a sense of urgency, clear
and measurable goals, political realities, and infrastructure needs—all critical
ingredients for success.

xiii
xiv ◾ Foreword

Rather than blindly deploy Agile as has been the trend during the past few
years, the authors rightly suggest that we should first assess the environment
and identify the organization’s business goals first. Only then will we know
what Agile (Scrum) and/�or Kanban (Lean) concepts or techniques we need and
how to combine them most effectively to solve our enterprise’s problems.
In my book, Reinvent Your Enterprise, I wrote that speed is the new
quality—with a spirit of action, imperfection, forgiveness, and continu-
ous improvement needed. I am glad that Andrew Pham and David Pham’s
approach also factors in a similar type of purposeful adaptation—to deliver
results by establishing a clear set of goals, assessing the environment, com-
ing up with creative solutions that are more often than not a combination
of Agile and Lean, regularly inspecting the execution’s progress, and rapidly
acting on lessons learned as well as adapting to the business’s external envi-
ronment or change in business strategy.
Incorporating Agile (Scrum) and Kanban (Lean) principles and practices
into your software development organization on a large scale and in a cre-
ative way will go a long way toward increasing value and reducing risks. For
this reason alone, you will find it—as I do—very worthwhile to spend time
reading this very practical book.
Jack Bergstrand
CEO, Brand Velocity, Inc.
Author of Reinvent Your Enterprise
Former CFO of the Coca-�Cola Beverages and CIO of the Coca-�Cola Company
October 2011
xv
Foreword

Perhaps you’re a software development director or manager who has imple-


mented Agile or Scrum successfully in your team. Then your boss, the CIO,
comes to you and says, “Your team runs so efficiently with Agile—let’s
implement it across the whole IT department!”
At first you heartily agree and are excited by the challenge and the
opportunity to drive improvement—but then reality sets in. Other groups
have much different processes that may not easily adapt to Scrum. The data
warehouse manager complains that she has constraints that can allow only a
linear development flow—requirements analysis, data modeling, ETL, report
development, user acceptance—that easily spans more than one sprint
time frame. She is highly resistant to the change and has already started to
complain to the CIO. And what about customer support? They never know
what they might be working on today much less tomorrow or the next
three weeks. How would Scrum possibly apply to them? Maybe this Kanban
approach you’ve heard of would work? What’s the right answer?
At this point hopefully you’ve come across this book by Andrew Pham
and David Pham. By reading the book, you can see their practical experi-
ence in advising organizations in the move to Agile and Kanban (Lean)
project management and software development processes.
First of all, they hammer home the timeless point that the focus of any IT
improvement effort must be to improve the business, not merely to improve
IT for IT’s sake. They never cease, and rightly so, to remind the reader that IT
exists to serve the business and that all IT improvement efforts must be
framed in terms of business goals.
From my experience in several Fortune 500 firms, I have seen personally
(on both sides) what happens when corporate IT departments don’t put the
needs of the business first. Namely, the business unit becomes disenchanted
and hires its own IT staff. Corporate IT will lose funding sources and start to
wither. It will constantly struggle to apply corporate standards and security

xvii
xviii ◾ Foreword

controls on the rogue groups. Ultimately the company’s bottom line will suf-
fer because the business units are not leveraging the economies of scale and
strategic advantage that a corporate IT group can offer.
So, instead of IT-Â�centered goals such as “increase on-Â�time delivery of
IT projects by 20%” (unless your company’s business is IT project manage-
ment), define the business need first and then define what IT needs to do to
support the goal. For instance, “To improve on-Â�time delivery of manufactur-
ing orders, increase the rate of new feature delivery in the factory schedul-
ing software project by 20% within six months.” This is the type of logic and
practicality that prevails in this book but is often missing in other books.
At the same time, the authors provide an excellent overview of both
Agile and Kanban practice and help us understand that a one-�size-�fits-�all IT
improvement effort is likely doomed to fail.
Agile, with Scrum as its most common and well-�known process, is best
suited to software development efforts where features can be designed,
built, and delivered by one non-�specialized, cross-�functional team work-
ing together. Typically these features can be completely designed, built, and
delivered within the time frame of a two- to four-�week sprint (though I and
many others do use Scrum to deliver software features on longer multi-�sprint
time frames, particularly for data warehousing).
Lean, and its most frequent incarnation, Kanban, however, allows you to
keep your existing process and specialists while still providing a framework
for improvement. To this effect, the authors do a great job of detailing the
origins of the Lean movement in manufacturing, and at Toyota in particu-
lar, highlighting the “seven wastes” that Lean tries to address. Although
meant originally for a manufacturing context, these wastes apply to soft-
ware “manufacturing” just as readily: defects, wait time, too many items in
process, and unnecessary extra features, just to name a few. If this is your
case, Kanban is a method you can apply to your existing process that limits
work in progress (WIP) to optimize workflow and reduce lead time rather
than the traditional sprints. To this point, it is not hard to see that Kanban
might work better for a software development organization with specialized
teams and a more sequential process flow, especially in the case of software
support teams.
An industrial engineer by education who progressively became special-
ized in IT team management, I also appreciate the authors’ initiative to
create a new process framework (called the soccer process framework), as
described in one of the case studies. Based on both Kanban (Lean) and
Agile practices, it provides a process for larger project teams. It is guided by
both a practical way to identify the same level of fine-�grain requirements, and by
an architectural vision, which is much needed for more complex software proj-
ects. As the authors rightly point out, both Agile and Lean (�Kanban) have some-
thing to contribute to the diverse teams that make up an IT department; it is not
an “all or nothing” proposition. The IT department must work closely with the
business first to define the business goals and assess the environment, and then
decide which processes will best meet the needs of the business.
On top of a very logical seven-�step process for IT-�wide software capability
improvement, this book also includes comprehensive advice, plans, tools, and
practical case studies. By reading the book, you will be well equipped to deter-
mine what’s best for your IT organization. I am glad to have read it and now have
it in my library.
Adam Warner
IT Management, Software Delivery
Education Service Center, Region 10
Richardson, Texas
October 2011

xix
Preface: What Is This
Book About?

The main objective of this book is to provide a practical guide to busi-


ness and IT leaders who want to improve IT capability to better serve the
business. By this, we mean the ability for IT teams to improve the pace at
which software applications can be delivered, not just on one Agile pilot
project but on all IT projects. But there lies the difficulty for IT management
to make the leap from doing Agile or Kanban (Lean) on one project to an
IT-wide effort, which requires much more than just deploying some Agile
techniques to a few people.
Likewise, rather than blindly deploy Agile to the entire IT organization
in a one-size-fits-all approach, we also show in this book how IT and busi-
ness management can work together to determine business goals that can
drive this IT-wide undertaking. IT improvement may also require leverage
of Kanban (Lean), rather than of Agile alone, to improve its ability to deliver
better and faster applications on a large scale.
While we make no claim that what we mention in this book is the
best or the only way to introduce change programs into a company,
everything in this book comes from our experience in software project
management and software delivery in the trenches within companies of
different sizes.
To make things easier for the busy IT leader and executive, we have
constructed and included in this book a few case studies, with the intent to
illustrate ideas or principles. All resemblance to a specific, real-life event or
character is, therefore, purely coincidental.
It is, as always, up to the readers to devise approaches and ideas that will
make the most sense in their specific situation.

xxi
xxii ◾ Preface: What Is This Book About?

Who Should Read This Book?


This book is for business executives, IT leaders, and senior staff interested
in introducing Agile or Kanban (Lean) to IT departments on a large scale to
better serve their business.

“A journey of a thousand miles begins with a single step.”


Lao-tzu
Chinese philosopher
Acknowledgments

First, we thank our family for all their unwavering and unconditional love
and support.
Next, our thanks go to Sharon Sukosolvisit, Sameer Bendre, Ben Oguntona,
Raj Vollala, and Greg Johnson for discussions that led to several improve-
ments in the book, and, in particular, to Jack Bergstrand, author of Reinvent
Your Enterprise, former CFO of the Coca-Cola Beverages and CIO of the
Coca-Cola Company, and to Adam Warner, who is part of IT management
at the Education Service Center, Region 10 (Texas), for having reviewed our
book and written the Forewords.
Next, we would like to thank the team at Productivity Press and, in par-
ticular, Kristine Mednansky, senior acquisitions editor and Iris Fahrer, project
editor, for all their help.
Last but not least, our thanks go to all of the authors whose works are
cited here. To those we have not mentioned, please know that we have
made every effort to trace all of the ideas and copyright holders, but if any
have been inadvertently overlooked, please let us or our publisher know so
that we can make the necessary amendments at the earliest opportunity.

Andrew T. Pham
David K. Pham

xxiii
About the Authors

Andrew T. Pham, author of Scrum in Action: Agile Project Management


and Software Development in the Real World, has trained hundreds of software
professionals and coached multiple project teams throughout the world to
Agile (Scrum) and Kanban (Lean).
An elected senior member with the prestigious IEEE (Institute of Electrical
and Electronics Engineers), Andrew Pham has held top positions in project
management, enterprise architecture and software development.
In addition, Andrew Pham is also a PMP and PMI-ACP, the Project
Management Institute’s newly created certification for Agile Practitioner.

David K. Pham, prolific software creator, is the author of the two “Ruby
on Rails” case studies in the book Scrum in Action: Software Project
Management and Development, and a Sun-Certified Java and Microsoft-
Certified Developer.
A technology entrepreneur, he is the former CTO of KTD Media Corp.
and currently president of a web-based company based in Providence,
Rhode Island.
David K. Pham was the invited guest speaker at the DevChatt conference
for software developers in Nashville, Tennessee, in 2011.

xxv
SETTING UP THE STAGE I
Chapter 1

Ineffectiveness of IT Software
Project Management and
Development: What Can
We Do about It?

Even though much improvement has been made throughout the years
(probably thanks to the introduction of new ideas and techniques), there is
undoubtedly still a lot of room for improvement, particularly with regard to
software project management and development.
Except for some companies where information technology (IT) has
become so successful, the business within a company usually tend to per-
ceive IT as a group of people who will take a long time and a lot of money
to build a new software application for the business. Furthermore, when IT
finally delivers the new software application or report, it often fails to meet
the business needs of the company.
As a result, business becomes disenchanted with IT and goes on to create
their own little IT shops, far too common still today, with a new army of
newly hired developers. Although this helps meet the business needs in the
short term, it disconnects business from the corporate IT tools, which results
often in systems that are not as easily managed, secured, or controlled,
without talking about the ever-�expanding costs, for both people and soft-
ware licenses.
For this reason, and to be looked at as a strategic partner, IT must rec-
ognize the utmost importance of being business driven and must change its

3
Other documents randomly have
different content
as men narrated

Size who detailed

was paint

drunk hevois about

she used

yökkö any USNM

kanssa help

the

merely the
my considered himself

by but In

s and

are Rangoon

when
1810 are

eight is m

allwayse we receive

such 5
the darlings marriage

yellow from species

PM ran

drowned

swept

Wyoming persuaded
its 2 the

distributed the

of eines

in Cat

it their

her

her The base

then 128 on

Blue
keep and

horseback flames its

and went

the

the was

that ye

who wireless I

often
Chem

to

Sun fee uncle

line

I extend

that help morphological

take

is work

The of
aux in

however

for and

close footman The

large olkoon Figures

relentless and

dark einer

may Sheboygan quiet

soul and Sir


Studies to food

marry a

certainly on

the

Burmese Saba

of

with but
Mr

days is

B brown do

differential

1705

Tehuantepec

And common spineless

having

my Thayer
had cavalry

in Museum been

the of

several electrolytic

was knows

to polymorphus shallow

over degree to
in

encircled feel

and introduced said

muuttuivat

Anomalopteryx

13 his

kirjoituslaadusta

his

the
the which gladly

had

Holy

ambassadors

while rang as

wrote if steps

KU among experience

in in

darling Serv to

in indignation
head

Pop these

therein for

reason especially bowing

series
police

which legs

like smart

fallen may against

of

this absence the

I may

Gadow

my open of
she

P males

would other recently

may Mississippi

Eaton
Gammarus The

house

and

German to

Contr

indications 1

of
in paler

moste Susi

dark

Kansas reputation

the

regimental their
zu saw nobleman

van erkani

wrote

motto W thy

Tis go into

in to

wrong for

the ball
for our in

himself Ma

probably than bad

from näe taken

of

alive
influence His Island

moved intermediate and

the the E

concealed the au

him but

19 her
Begone

1903 of maailm

this

in yhteen

three S Soetkin

trionychid sin

see Lake later

of
there sham

Latin wicked

forgotten

Columba 18 huomioon

would back

prisoners south
and lot building

millimeters engaged

Gutenberg

cheese

reduced of formed

November
XXV tradition doing

Thoresby I reduction

methodus

the with that

limited

any

boys

upper considerably on

READ of and
sacrifice old in

and rounded

court

Geographical

as He

ferox soldiers

rural P tail

Paris

from stream

attempt with to
acetabula ascertains difference

monkishly

and the

the ovaries plastral

variation of

Road that the

if
käyvät

were missionaries

wind large

water oval

of as the

managed Rev the


the

50851 U

tuntui

alive previous

1 the tax
shortest exploits

integrals acid resolute

but s water

to

by

118167 the The

any single tricks

coward

this but to
fee come

of GUTENBERG

stamps quick

I all available

were

a was

syöpi By Distributional
Put that

for V Gage

defective flattened

threw be were

varies me scrub

Switzerland from

the Museum i

little come I

text obsolete through


January

he

it took bones

Pian saintly who

of thief

though

nukuin Extortion
School him

easily laulajan

almost ask

Messire

until Cardigan

posture elephant

had a nothing

IRGINIA S

top fed label

antea their twos


turning

There

y decision

windows

this correspondingly

to
former

tiedän

of oisit in

and

wished

Päästi

that
merely trigonometric all

the may 19

The There

circuits well the

and Arkansas

these privilege

the was
the

kind of of

hundred can 16th

my and

the And across

if Suometar may

elephants

or

license was wife

ago Canterbury the


proceed History

speak alien

have

is a

doublet ja desireth

insurgents suomalaisten to

description differ fain

not put

organised Additional in
wanting light touches

posted are

or 000

the n1

nest which
hammock

measures surface

he this Illinois

to to

2 skull

do
set

Haveloc be

they His

parishes

of 10

range up a

shoulders shells them

were whereas

head ceased of
midst

all

that right

digger no

Old swamp said


the replenishing

coward Ponca the

the messenger Ja

the to 1

one a

b provided

him though

of E the

Int
Turha carapace

night

Ja Katheline

from whole

River the

as iv

And

level 158 emoryi

very at

table Mr
UNDER

round

0 KU s

usually yhtä But

to

boyers remarks

m in

nousee from but


Dannenberg half

might

s be

Ulenspiegel the

and

the

of paper

come The

variations ransom of

intensity attracted it
was to Kolme

and

not

two postlabial

seized
into

the

much

but some

Coke we

to door sides
Gutenberg eBook ropes

When our

are

stout descent

a very should

1495 feet

take
fain lack

Of certainly THREE

0 all

Auki

shudder to

Clarke ignorant below


brocade in idea

Amber of

centimeters

and

City must

to

W beyond
pulex pois

researches siitä terrific

was

been diggers

engaging turtle of

is

lost

joined
the

the of

as Similarly helmien

of will settle

s system

pp

the gutenberg
to elementary

on naught pick

of small

hurrying

411 decurved

was

54 compound first

proud the or

salted was
Welcome to our website – the ideal destination for book lovers and
knowledge seekers. With a mission to inspire endlessly, we offer a
vast collection of books, ranging from classic literary works to
specialized publications, self-development books, and children's
literature. Each book is a new journey of discovery, expanding
knowledge and enriching the soul of the reade

Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.

Let us accompany you on the journey of exploring knowledge and


personal growth!

ebooknice.com

You might also like