libri scuola books Fumetti ebook dvd top ten sconti 0 Carrello


Torna Indietro

pham andrew thu; pham david khoi - business-driven it-wide agile (scrum) and kanban (lean) implementation

Business-Driven IT-Wide Agile (Scrum) and Kanban (Lean) Implementation An Action Guide for Business and IT Leaders

;




Disponibilità: Normalmente disponibile in 20 giorni
A causa di problematiche nell'approvvigionamento legate alla Brexit sono possibili ritardi nelle consegne.


PREZZO
55,98 €
NICEPRICE
53,18 €
SCONTO
5%



Questo prodotto usufruisce delle SPEDIZIONI GRATIS
selezionando l'opzione Corriere Veloce in fase di ordine.


Pagabile anche con Carta della cultura giovani e del merito, 18App Bonus Cultura e Carta del Docente


Facebook Twitter Aggiungi commento


Spese Gratis

Dettagli

Genere:Libro
Lingua: Inglese
Pubblicazione: 08/2012
Edizione: 1° edizione





Note Editore

Business-Driven IT-Wide Agile (Scrum) and Kanban (Lean) Implementation: An Action Guide for Business and IT Leaders explains how to increase IT delivery capabilities through the use of Agile and Kanban. Factoring in constant change, communication, a sense of urgency, clear and measurable goals, political realities, and infrastructure needs, it covers all the ingredients required for success. Using real-world examples, this practical guide illustrates how to implement Agile and Kanban in software project management and development across the entire IT department. To make things easier for busy IT leaders and executives, the text includes two case studies along with numerous templates to facilitate understanding and kick-start implementation. Explaining how IT and business management can work together to determine business goals that drive this IT-wide undertaking, the book arms you with actionable solutions that can be put to use immediately in any IT department, regardless of size.




Sommario

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 NutshellSo, What Is Lean and What Is Kanban? So, What Is Lean? So, What Is Kanban? Kanban Practices in a NutshellSimilarities between Agile/Scrum and KanbanSummaryEndnotes Why Agile Alone May Not Be Enough or the Right Solution, and Why Implementing Agile or Kanban without Good Business Objectives Will Normally FailWhy 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 LearnedFrom 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 Out Kanban Came to the RescuePitfalls 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 FrameworkDescription Step 1: Identify the Business Sponsor and Her or His Needs and Goals Identify the Business Sponsor Identify Business Problems and Issues Identify Business and IT Goals Identify MeasurementsStep 2: Perform Environment Boundary Identification and Assessment Identify the Boundary Environment Assessment Findings SummaryStep 3: Envision Scenarios and RisksStep 4: Detail the Chosen Action PlanStep 5: Implement the Chosen Action PlanStep 6: Inspect the Implementation’s ProgressStep 7: Adapt the Chosen Action Plan (as Needed)Summary Step 1: Identify the (Business) Sponsor and Her or His Needs and GoalsIdentify the (Business) Sponsor(s)Identify the Sponsor(s)’ Needs and GoalsSummary Step 2: Perform Environment Boundary Identification and AssessmentHow to Identify the Environment BoundaryAssess the Identified Business and IT EnvironmentFindings SummarySummary Step 3: Envision Scenarios and RisksFrom Goals to Action Items (in Bypassing the Assessment)How to Identify Risks (for Different Scenarios)Scenario ConsolidationSummary Step 4: Detail the Chosen Action PlanAnatomy of a Detailed Scenario (Chosen Action Plan)The Seven Characteristics of a Good Action PlanSummary Step 5: Implement the Chosen Action PlanSet Up the Implementation StructureSeven Characteristics of an Effective Plan ExecutionSummary Step 6: Inspecting the Implementation’s ProgressWhy Is Regular Progress Inspection Critical?What to Inspect At the Overall Plan Level At the Action Item LevelSummary Step 7: Adapt the Chosen Action Plan (as Needed)Different Types of Change Strategic Change Operational ChangeExamples of Adaptations Strategic Impact Operational ImpactSummary RETROSPECTIVES Lessons Learned CASE STUDIESCase 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 SummaryStep 3: Envision ATP ScenariosStep 4: Develop the Detailed Action Plan for ATPStep 5: Execute the ATP Action PlanStep 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 DimensionsStep 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 StrategyLessons Learned APPENDICES Appendix A: From the Project Management Office to the Project 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 EstimateAppendix B: Change Management Appendix C: Two Most Important Tools of a Good Software Development Infrastructure Continuous Integration Automated TestingGlossaryBibliography Index




Autore

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 to the above, 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, hewas formerly the CTOof KTD Media Corp. and currently president of a web-based companyin Providence, Rhode Island. David K. Pham was the invited guest speaker at the DevChatt conference for software developers in Nashville, Tennessee in 2011. He can be contacted at hello@davidkpham.com.










Altre Informazioni

ISBN:

9781466557482

Condizione: Nuovo
Dimensioni: 10 x 7 in Ø 0.80 lb
Formato: Brossura
Illustration Notes:118 b/w images
Pagine Arabe: 196


Dicono di noi