Download Free Forming Agile Teams Workbook Black And White Book in PDF and EPUB Free Download. You can read online Forming Agile Teams Workbook Black And White and write the review.

Project retrospectives help teams examine what went right and what went wrong on a project. But traditionally, retrospectives (also known as “post-mortems”) are only held at the end of the project—too late to help. You need agile retrospectives that are iterative and incremental. You need to accurately find and fix problems to help the team today. Now Esther and Diana show you the tools, tricks and tips you need to fix the problems you face on a software development project on an on-going basis. You’ll see how to architect retrospectives in general, how to design them specifically for your team and organization, how to run them effectively, how to make the needed changes and how to scale these techniques up. You’ll learn how to deal with problems, and implement solutions effectively throughout the project—not just at the end. This book will help you: Design and run effective retrospectives Learn how to find and fix problems Find and reinforce team strengths Address people issues as well as technological Use tools and recipes proven in the real world With regular tune-ups, your team will hum like a precise, world-class orchestra.
Effective software teams are essential for any organization to deliver value continuously and sustainably. But how do you build the best team organization for your specific goals, culture, and needs? Team Topologies is a practical, step-by-step, adaptive model for organizational design and team interaction based on four fundamental team types and three team interaction patterns. It is a model that treats teams as the fundamental means of delivery, where team structures and communication pathways are able to evolve with technological and organizational maturity. In Team Topologies, IT consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions to help readers choose and evolve the right team patterns for their organization, making sure to keep the software healthy and optimize value streams. Team Topologies is a major step forward in organizational design for software, presenting a well-defined way for teams to interact and interrelate that helps make the resulting software architecture clearer and more sustainable, turning inter-team problems into valuable signals for the self-steering organization.
UX design has traditionally been deliverables-based. Wireframes, site maps, flow diagrams, content inventories, taxonomies, mockups helped define the practice in its infancy.Over time, however, this deliverables-heavy process has put UX designers in the deliverables business. Many are now measured and compensated for the depth and breadth of their deliverables instead of the quality and success of the experiences they design. Designers have become documentation subject matter experts, known for the quality of the documents they create instead of the end-state experiences being designed and developed.So what's to be done? This practical book provides a roadmap and set of practices and principles that will help you keep your focus on the the experience back, rather than the deliverables. Get a tactical understanding of how to successfully integrate Lean and UX/Design; Find new material on business modeling and outcomes to help teams work more strategically; Delve into the new chapter on experiment design and Take advantage of updated examples and case studies.
The Provocative and Practical Guide to Coaching Agile Teams As an agile coach, you can help project teams become outstanding at agile, creating products that make them proud and helping organizations reap the powerful benefits of teams that deliver both innovation and excellence. More and more frequently, ScrumMasters and project managers are being asked to coach agile teams. But it’s a challenging role. It requires new skills—as well as a subtle understanding of when to step in and when to step back. Migrating from “command and control” to agile coaching requires a whole new mind-set. In Coaching Agile Teams, Lyssa Adkins gives agile coaches the insights they need to adopt this new mind-set and to guide teams to extraordinary performance in a re-energized work environment. You’ll gain a deep view into the role of the agile coach, discover what works and what doesn’t, and learn how to adapt powerful skills from many allied disciplines, including the fields of professional coaching and mentoring. Coverage includes Understanding what it takes to be a great agile coach Mastering all of the agile coach’s roles: teacher, mentor, problem solver, conflict navigator, and performance coach Creating an environment where self-organized, high-performance teams can emerge Coaching teams past cooperation and into full collaboration Evolving your leadership style as your team grows and changes Staying actively engaged without dominating your team and stunting its growth Recognizing failure, recovery, and success modes in your coaching Getting the most out of your own personal agile coaching journey Whether you’re an agile coach, leader, trainer, mentor, facilitator, ScrumMaster, project manager, product owner, or team member, this book will help you become skilled at helping others become truly great. What could possibly be more rewarding?
This is a comprehensive guide to Scrum for all (team members, managers, and executives). If you want to use Scrum to develop innovative products and services that delight your customers, this is the complete, single-source reference you've been searching for. This book provides a common understanding of Scrum, a shared vocabulary that can be used in applying it, and practical knowledge for deriving maximum value from it.
What's it like to work on a great software development team facing an impossible problem? How do you build an effective team? Can a group of people who don't get along still build good software? How does a team leader keep everyone on track when the stakes are high and the schedule is tight? Beautiful Teams takes you behind the scenes with some of the most interesting teams in software engineering history. You'll learn from veteran team leaders' successes and failures, told through a series of engaging personal stories -- and interviews -- by leading programmers, architects, project managers, and thought leaders. This book includes contributions from: Tim O'Reilly Scott Berkun Mark Healey Bill DiPierre Andy Lester Keoki Andrus Tom Tarka Auke Jilderda Grady Booch Jennifer Greene Mike Cohn Cory Doctorow Neil Siegel Trevor Field James Grenning Steve McConnell Barry Boehm and Maria H. Penedo Peter Gluck Karl E. Wiegers Alex Martelli Karl Fogel Michael Collins Karl Rehmer Andrew Stellman Ned Robinson Scott Ambler Johanna Rothman Mark Denovich and Eric Renkey Patricia Ensworth Andy Oram Tony Visconti Beautiful Teams is edited by Andrew Stellman and Jennifer Greene, veteran software engineers and project managers who have been writing bestselling books for O'Reilly since 2005, including Applied Software Project Management, Head First PMP, and Head First C#.
“We need better approaches to understanding and managing software requirements, and Dean provides them in this book. He draws ideas from three very useful intellectual pools: classical management practices, Agile methods, and lean product development. By combining the strengths of these three approaches, he has produced something that works better than any one in isolation.” –From the Foreword by Don Reinertsen, President of Reinertsen & Associates; author of Managing the Design Factory; and leading expert on rapid product development Effective requirements discovery and analysis is a critical best practice for serious application development. Until now, however, requirements and Agile methods have rarely coexisted peacefully. For many enterprises considering Agile approaches, the absence of effective and scalable Agile requirements processes has been a showstopper for Agile adoption. In Agile Software Requirements, Dean Leffingwell shows exactly how to create effective requirements in Agile environments. Part I presents the “big picture” of Agile requirements in the enterprise, and describes an overall process model for Agile requirements at the project team, program, and portfolio levels Part II describes a simple and lightweight, yet comprehensive model that Agile project teams can use to manage requirements Part III shows how to develop Agile requirements for complex systems that require the cooperation of multiple teams Part IV guides enterprises in developing Agile requirements for ever-larger “systems of systems,” application suites, and product portfolios This book will help you leverage the benefits of Agile without sacrificing the value of effective requirements discovery and analysis. You’ll find proven solutions you can apply right now–whether you’re a software developer or tester, executive, project/program manager, architect, or team leader.
Information Design Workbook, Revised and Updated provides an up-to-date guide on creating visually compelling and useful graphics.
From the New York Times bestselling author of My Share of the Task and Leaders, a manual for leaders looking to make their teams more adaptable, agile, and unified in the midst of change. When General Stanley McChrystal took command of the Joint Special Operations Task Force in 2004, he quickly realized that conventional military tactics were failing. Al Qaeda in Iraq was a decentralized network that could move quickly, strike ruthlessly, then seemingly vanish into the local population. The allied forces had a huge advantage in numbers, equipment, and training—but none of that seemed to matter. To defeat Al Qaeda, they would have to combine the power of the world’s mightiest military with the agility of the world’s most fearsome terrorist network. They would have to become a "team of teams"—faster, flatter, and more flexible than ever. In Team of Teams, McChrystal and his colleagues show how the challenges they faced in Iraq can be rel­evant to countless businesses, nonprofits, and or­ganizations today. In periods of unprecedented crisis, leaders need practical management practices that can scale to thousands of people—and fast. By giving small groups the freedom to experiment and share what they learn across the entire organiza­tion, teams can respond more quickly, communicate more freely, and make better and faster decisions. Drawing on compelling examples—from NASA to hospital emergency rooms—Team of Teams makes the case for merging the power of a large corporation with the agility of a small team to transform any organization.
When project managers are faced with budget cuts and fewer resources, waste elimination becomes a priority in maintaining effectiveness. This does not mean shortening or abandoning traditional project cycles. In fact, fast results on critical assignments can only be completed with strong plans and a detailed work breakdown structure. The connections, or lack thereof, are what strongly impact performance and quality. Lean and Agile, as covered in this book, are meant to enhance traditional project management, not replace the science. A strong foundation in traditional project management is necessary to appreciate the benefits of adopting Lean and Agile. Lean and Agile Project Management: How to Make Any Project Better, Faster, and More Cost Effective defines the wastes and issues found in project management and demonstrates how they can be addressed by engaging Lean thinking and Agile techniques. This book also: • Shows how to apply Lean principles to project management (PM) • Teaches the application of simple Six Sigma metrics in PM • Discusses the adoption of Agile techniques in PM in order to stay on task and remain flexible • Helps readers discover the theoretical synergies between popular PM programs • Promotes an understanding of how Lean people skills can help a person become a better leader and manager Since the publication of the first edition of this book, the bodies of knowledge have all been systematically updated. In addition, through conducting peer groups and detailed workshops, the Author has simplified many of the basics, and they are now much easier to understand. Essentially, the Author believes traditional project management can benefit from adding Lean and Agile, but she has simplified the model for greater efficiency.