Muutke küpsiste eelistusi

Agile Project Management with Kanban [Pehme köide]

  • Formaat: Paperback / softback, 160 pages, kõrgus x laius x paksus: 226x185x8 mm, kaal: 260 g
  • Sari: Developer Best Practices
  • Ilmumisaeg: 02-Apr-2015
  • Kirjastus: Microsoft Press,U.S.
  • ISBN-10: 0735698953
  • ISBN-13: 9780735698956
  • Formaat: Paperback / softback, 160 pages, kõrgus x laius x paksus: 226x185x8 mm, kaal: 260 g
  • Sari: Developer Best Practices
  • Ilmumisaeg: 02-Apr-2015
  • Kirjastus: Microsoft Press,U.S.
  • ISBN-10: 0735698953
  • ISBN-13: 9780735698956
Use Kanban to maximize efficiency, predictability, quality, and value With Kanban, every minute you spend on a software project can add value for customers. One book can help you achieve this goal:  Agile Project Management with Kanban.   Author Eric Brechner pioneered Kanban within the Xbox engineering team at Microsoft. Now he shows you exactly how to make it work for your team.   Think of this book as Kanban in a box: open it, read the quickstart guide, and youre up and running fast. As you gain experience, Brechner reveals powerful techniques for right-sizing teams, estimating, meeting deadlines, deploying components and services, adapting or evolving from Scrum or traditional Waterfall, and more.   For every step of your journey, youll find pragmatic advice, useful checklists, and actionable lessons. This truly is Kanban in a box: all you need to deliver breakthrough value and quality.   Use Kanban techniques to:



Start delivering continuous value with your current team  and project Master five quick steps for completing work backlogs Plan and staff new projects more effectively Minimize work in progress and quickly adjust to change Eliminate artificial meetings and prolonged stabilization Improve and enhance customer engagement Visualize workflow and fix revealed bottlenecks Drive quality upstream Integrate Kanban into large projects Optimize sustained engineering (contributed by James Waletzky) Expand Kanban beyond software development
Introduction ix
Chapter 1 Getting management consent 1(6)
An open letter to your manager
2(2)
Problem
2(1)
Solution
2(1)
Risks
3(1)
Plan
3(1)
Moving forward
4(1)
Checklist
5(2)
Chapter 2 Kanban quick-start guide 7(18)
Step 1: Capture your team's high-level routine
7(1)
Step 2: Redecorate your wall
8(2)
Step 3: Set limits on chaos
10(3)
Step 4: Define done
13(1)
Step 5: Run your daily standup
14(3)
Troubleshooting
17(7)
Checklist
24(1)
Chapter 3 Hitting deadlines 25(14)
Populate your backlog
25(2)
Establish your minimum viable product (MVP)
27(1)
Order work, including technical debt
28(1)
Estimate features and tasks
29(2)
Track expected completion date
31(2)
Right-size your team
33(4)
Basic approach
34(1)
Advanced approach
35(2)
Checklist
37(2)
Chapter 4 Adapting from Waterfall 39(18)
Introducing Kanban to a Waterfall team
39(3)
Working in feature teams
42(1)
Completing features before starting new ones
43(1)
Dealing with specs and bugs
44(2)
Specs
44(1)
Bugs
45(1)
Engaging with customers
46(2)
Celebrating performance improvements
48(3)
Rude Q & A
51(5)
Checklist
56(1)
Chapter 5 Evolving from Scrum 57(14)
Introducing Kanban to a Scrum Team
58(2)
Mapping the roles and terms
60(1)
Evolving the events
61(1)
Celebrating performance improvements
62(3)
Rude Q & A
65(5)
Checklist
70(1)
Chapter 6 Deploying components, apps, and services 71(14)
Continuous integration
72(3)
Continuous push
75(2)
Continuous publishing
77(2)
Continuous deployment
79(4)
Checklist
83(2)
Chapter 7 Using Kanban within large organizations 85(16)
Deriving a backlog from big upfront planning
86(1)
Ordering work based on dependencies
87(4)
Fitting into milestones
91(1)
Communicating status up and out
92(2)
Dealing with late or unstable dependencies
94(4)
Late dependencies
94(1)
Unstable dependencies
95(3)
Staying productive during stabilization
98(2)
Checklist
100(1)
Chapter 8 Sustained engineering 101(16)
Define terms, goals, and roles
101(3)
Consistent vocabulary
102(1)
Challenges and goals
102(1)
Define roles and responsibilities
103(1)
Determine SE ownership
104(1)
Lay out support tiers
105(1)
Tier 1
106(1)
Tier 2
106(1)
Tier 3
106(1)
Collaborate for efficiency
106(2)
Triage
106(2)
Quick-solve meeting
108(1)
Implement Kanban SE workflow
108(3)
Escalations
109(1)
Bugs/Other Work
109(2)
Kanban tools
111(1)
Troubleshooting
112(3)
Checklist
115(2)
Chapter 9 Further resources and beyond 117(20)
Expanding Kanban to new areas of business and life
117(3)
Scaling Kanban up, down, and out
118(2)
Personal Kanban
120(1)
Mixing Agile and Lean with Kanban
120(3)
Why Kanban works
123(5)
Single-piece flow
124(1)
Theory of constraints (TOC)
124(2)
Drum-buffer-rope
126(2)
Improving beyond Kanban
128(8)
Critical chain
129(1)
Lean development
130(2)
Global optimization
132(4)
Checklist
136(1)
Index 137(8)
About the author 145
Eric Brechner is the development manager for Microsofts Xbox Engineering Services team. At Microsoft, he has also been development manager for Xbox.com, engineering learning and development, and Office Media Store. He has previously worked at Boeing, Silicon Graphics, Graftek, and Jet Propulsion Laboratory. The author of a book and blog on software best practices (as I. M. Wright), he holds eight patents and a Ph.D. in applied mathematics.