|
|
|
|
| LEADER |
00000cam a2200000Ma 4500 |
| 001 |
OR_ocn849028211 |
| 003 |
OCoLC |
| 005 |
20231017213018.0 |
| 006 |
m o d |
| 007 |
cr zn||||||||| |
| 008 |
130603s2013 flua ob 001 0 eng d |
| 040 |
|
|
|a B24X7
|b eng
|e pn
|c B24X7
|d OCLCO
|d UMI
|d OCLCQ
|d OCLCF
|d OCLCQ
|d LIV
|d NLE
|d COO
|d UKMGB
|d BRF
|d OCLCO
|d OCLCQ
|d OCLCO
|
| 015 |
|
|
|a GBB7A1275
|2 bnb
|
| 016 |
7 |
|
|a 018373065
|2 Uk
|
| 019 |
|
|
|a 904442226
|
| 020 |
|
|
|a 9781466557499
|
| 020 |
|
|
|a 1466557494
|
| 020 |
|
|
|a 9781466578555
|
| 020 |
|
|
|a 1466578556
|
| 020 |
|
|
|a 9781466578562
|
| 020 |
|
|
|a 1466578564
|
| 020 |
|
|
|z 9781466557482
|q (pbk.)
|
| 029 |
1 |
|
|a UKMGB
|b 018373065
|
| 035 |
|
|
|a (OCoLC)849028211
|z (OCoLC)904442226
|
| 037 |
|
|
|a CL0500000559
|b Safari Books Online
|
| 050 |
|
4 |
|a QA76.76.D47
|b P487 2013eb
|
| 082 |
0 |
4 |
|a 005.1
|2 23
|
| 049 |
|
|
|a UAMI
|
| 100 |
1 |
|
|a Pham, Andrew Thu.
|
| 245 |
1 |
0 |
|a Business-driven IT-wide agile (scrum) and Kanban (lean) implementation :
|b an action guide for business and IT leaders /
|c Andrew T. Pham and David K. Pham ; foreword[s] by Jack Bergstrand ... [and] Adam Warner.
|
| 260 |
|
|
|a Boca Raton, Fla. :
|b CRC Press,
|c ©2013.
|
| 300 |
|
|
|a 1 online resource
|
| 336 |
|
|
|a text
|b txt
|2 rdacontent
|
| 337 |
|
|
|a computer
|b c
|2 rdamedia
|
| 338 |
|
|
|a online resource
|b cr
|2 rdacarrier
|
| 500 |
|
|
|a "A Productivity Press book."
|
| 500 |
|
|
|a Title from title screen.
|
| 504 |
|
|
|a Includes bibliographical references and index.
|
| 505 |
0 |
|
|a SETTING UP THE STAGE Ineffectiveness of IT Software Project Management and Development: What Can We Do about It?; Why Are Command-and-Control and Waterfall Life Cycle Approaches Harmful When Used Together?; What Can We Do about It? Executive Summary of Agile (Scrum) and Kanban (Lean); So, What Is Agile?; Agile Manifesto; Example of a Known Agile Process: Scrum; Agile Practices in a Nutshell; So, What Is Lean and What Is Kanban?; So, What Is Lean?; So, What Is Kanban?; Kanban Practices in a Nutshell; Similarities between Agile/Scrum and Kanban; Summary; Endnotes Why Agile Alone May Not Be Enough or the Right Solution,
|
| 505 |
0 |
|
|a And Why Implementing Agile or Kanban without Good Business Objectives Will Normally Fail; Why Agile Alone May Not Be Enough (Preliminary Case Study #1); Initial Planning; Pilot Project Team; Initial Project Team Training; On-Site Scrum Workshop; Second Sprint: Another Hit for the Team!; Third Sprint: Things Started to Rumble; Fourth Sprint: Things Became Worse and Worse; Fifth Sprint: Project Was Cancelled!; Lessons Learned; From Scrum to Kanban (Preliminary Case Study #2); Context; Information Technology; There Is Nothing They Do Not Have; Feedback from the Trenches; Finally the Truth Came
|
| 505 |
0 |
|
|a Out; Kanban Came to the Rescue; Pitfalls of New Software Processes; Release and Sprint Planning; Scrum Ceremonies; First Month; Change in Product Owner; Different Understanding of Agile and Scrum; Building New Expectations; Nice Surprise; Agile Started to Rumble; Back to Waterfall and Command and Control BUSINESS GOALS-DRIVEN IT-WIDE SOFTWARE DELIVERY IMPROVEMENT FRAMEWORK Seven-Step Software Delivery Improvement Framework; Description; Step 1: Identify the Business Sponsor and Her or His Needs and Goals; Identify the Business
|
| 505 |
0 |
|
|a Sponsor; Identify Business Problems and Issues; Identify Business and IT Goals; Identify Measurements; Step 2: Perform Environment Boundary Identification and Assessment; Identify the Boundary; Environment Assessment; Findings Summary; Step 3: Envision Scenarios and Risks; Step 4: Detail the Chosen Action Plan; Step 5: Implement the Chosen Action Plan; Step 6: Inspect the Implementation’s Progress; Step 7: Adapt the Chosen Action Plan (as Needed); Summary Step 1: Identify the (Business) Sponsor and Her or His Needs and Goals; Identify the (Business) Sponsor(s); Identify the Sponsor(s)’ Needs and Goals; Summary Step 2: Perform Environment Boundary Identification
|
| 505 |
0 |
|
|a And Assessment; How to Identify the Environment Boundary; Assess the Identified Business and IT Environment; Findings Summary; Summary Step 3: Envision Scenarios and Risks; From Goals to Action Items (in Bypassing the Assessment); How to Identify Risks (for Different Scenarios); Scenario Consolidation; Summary Step 4: Detail the Chosen Action Plan; Anatomy of a Detailed Scenario (Chosen Action Plan); The Seven Characteristics of a Good Action Plan; Summary Step 5: Implement the Chosen Action Plan; Set Up the Implementation Structure; Seven Characteristics of an Effective Plan Execution; Summary Step 6: Inspecting the Implementation’s Progress; Why Is Regular Progress Inspection Critical?; What to Inspect; At the Overall Plan Level; At the Action Item
|
| 505 |
0 |
|
|a Level; Summary Step 7: Adapt the Chosen Action Plan (as Needed); Different Types of Change; Strategic Change; Operational Change; Examples of Adaptations; Strategic Impact; Operational Impact; Summary RETROSPECTIVES Lessons Learned CASE STUDIES; Case Study 1: "Customized Agile Combined with Kanban"; Step 1: Identify Business Sponsor and Her or His Needs and Goals; Step 2: Perform ATP’s Environment Boundary Identification and Assessment; ATP Process Improvement Effort’s Boundary; Environment Assessment; Findings Summary; Step 3: Envision ATP Scenarios; Step 4:
|
| 505 |
0 |
|
|a Develop the Detailed Action Plan for ATP; Step 5: Execute the ATP Action Plan; Step 6: Inspect ATP Execution’s Progress; Identify and Mitigate Risks; Organize Effective Retrospectives and Learn from Their Lessons; Inspect the Actual Budget to Watch Out for Variance; Watch Out for Positive (and Less than Positive) Changes; Coming from the Different Dimensions; Step 7: Adapt the WTR Action Plan; Changes Coming from the Action Items and the Environment Reaction to the Action Plan; Organizational; Process; Change Due to Change in Business and/or IT Strategy; Lessons Learned APPENDICES Appendix A: From the Project Management Office to the Project
|
| 505 |
0 |
|
|a Delivery Office; Modify the Traditional Project Manager’s Job Description; Project Manager’s Traditional Job Description; Agile/Lean Project Manager’s New Job Description; Change the Way the PMO Calculates Its Project Estimate; ; Appendix B: Change Management Appendix C: Two Most Important Tools of a Good Software Development Infrastructure; Continuous Integration; Automated Testing; ; Glossa
|
| 590 |
|
|
|a O'Reilly
|b O'Reilly Online Learning: Academic/Public Library Edition
|
| 650 |
|
0 |
|a Agile software development.
|
| 650 |
|
0 |
|a Project management.
|
| 650 |
|
0 |
|a Information technology.
|
| 650 |
|
6 |
|a Méthodes agiles (Développement de logiciels)
|
| 650 |
|
6 |
|a Gestion de projet.
|
| 650 |
|
6 |
|a Technologie de l'information.
|
| 650 |
|
7 |
|a information technology.
|2 aat
|
| 650 |
|
7 |
|a Agile software development
|2 fast
|
| 650 |
|
7 |
|a Information technology
|2 fast
|
| 650 |
|
7 |
|a Project management
|2 fast
|
| 700 |
1 |
|
|a Pham, David Khoi.
|4 aut
|
| 700 |
1 |
|
|a Bergstrand, Jack.
|4 aui
|
| 700 |
1 |
|
|a Warner, Adam.
|4 aui
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781466557499/?ar
|z Texto completo (Requiere registro previo con correo institucional)
|
| 938 |
|
|
|a Books 24x7
|b B247
|n bks00051916
|
| 994 |
|
|
|a 92
|b IZTAP
|
