Agile Project Management with KanbanMicrosoft Press, 2015 M02 25 - 160 páginas 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 you’re 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, you’ll 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:
|
Contenido
| 1 | |
| 7 | |
Chapter 3 Hitting deadlines | 25 |
Chapter 4 Adapting from Waterfall | 39 |
Chapter 5 Evolving from Scrum | 57 |
Chapter 6 Deploying components apps and services | 71 |
Chapter 7 Using Kanban within large organizations | 85 |
Chapter 8 Sustained engineering | 101 |
Chapter 9 Further resources and beyond | 117 |
| 137 | |
About the author | 145 |
Otras ediciones - Ver todas
Términos y frases comunes
agility analyst approach apps Backlog Specify build changes Checklist completed tasks components continuous deployment core engineering team critical chain current task estimate customer feedback customer value customer-support daily standup meeting escalations feature team Global optimization high-level improvements Inside Xbox issues Kanban board Kanban quick-start guide large projects leadership Lean Software Development Little's Law longest step Microsoft milestones month move note cards pair programming partner teams planning planning poker priority Problem production-ready project manager quick-start guide Chapter refactoring release requirements resolve rude Q rules scenarios schedule Scrum Team signboard small batches specs sprint stabilization periods task add rate task completion rate Team Foundation Server team members team's test-driven development theory of constraints throughput Track column traditional Waterfall teams triage Troubleshooting typically unblock unit testing unresolved bugs unstable dependencies updates Validate weeks WIP limits work-item workflow
