Klik op een omslag om naar Google Boeken te gaan.
|
Bezig met laden... Create Your Succesful Agile Project: Collaborate, Measure, Estimate, Deliver (editie 2017)door Johanna Rothman (Auteur)
Informatie over het werkCreate Your Succesful Agile Project: Collaborate, Measure, Estimate, Deliver door Johanna Rothman
Geen Bezig met laden...
 Meld je aan bij LibraryThing om erachter te komen of je dit boek goed zult vinden. Op dit moment geen Discussie gesprekken over dit boek.  EmreSevinc | Mar 11, 2018 |  geen besprekingen | voeg een bespreking toe
You think agile techniques might be for you, but your projects and organization are unique. An "out-of-the-box" agile approach won't work. Instead, unite agile and lean principles for your project. See how to design a custom approach, reap the benefits of collaboration, and deliver value. For project managers who want to use agile techniques, managers who want to start, and technical leaders who want to know more and succeed, this book is your first step toward agile project success. You've tried to use an off-the-shelf approach to agile techniques, and it's not working. Instead of a standard method or framework, work from agile and lean principles to design your own agile approach in a way that works for you. Build collaborative, cross-functional teams. See how small batch sizes and frequent delivery create an environment of trust and transparency between the team, management, and customers. Learn about the interpersonal skills that help agile teams work together so well. In addition to seeing work and knowing what "done" means, you'll see examples of many possible team-based measurements. Look at tools you can use for status reporting, and how to use those measurements to help your managers understand what agile techniques buy them. Recognize the traps that prevent agile principles from working in too many organizations, and what to do about those traps. Use agile techniques for workgroups, and see what managers can do to create and nurture an agile culture. You might be surprised at how few meetings and rituals you need to still work in an agile way. Johanna's signature frankness and humor will get you on the right track to design your agile project to succeed. What You Need:No technical expertise or experience needed, just a desire to know more about how you might use agile in your project. Geen bibliotheekbeschrijvingen gevonden. |
Actuele discussiesGeenPopulaire omslagen
 Google Books — Bezig met laden...GenresDewey Decimale Classificatie (DDC)005.1Information Computing and Information Computer programming, programs, data, security ProgrammingLC-classificatieWaarderingGemiddelde: (3.5)
Ben jij dit?Word een LibraryThing Auteur. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
1
So, why bother with a book that's more than 250 pages? As with all things related to organizing humans, and setting up communication structures, persuading people to move to a different methodology, listening to an expert that has multi-decade experience helps. It especially helps when it is always possible to encounter traps and pitfalls, and when you need to to deal with ambiguity, as well as certainty arising from different aspects of work cultures in different companies.
Is this book perfect? No, not at all. If you want read a more concrete and focused case study [book:Lean from the Trenches|12693642] might be your cup of tea. Or if you want to go into the details of User Stories, then [book:User Stories Applied: For Agile Software Development|3856] might serve you better for that particular topic. Nevertheless, I still find Rothman's book valuable for its broad coverage, as well as its explanations on how simple concepts such as "velocity", "burn down charts", "delivering business value", "definition of done" can be misinterpreted and abused.
The chapter on applying an agile approach to workgroups, who are not teams, and who are not software-focused is also valuable, because it shows how the general principles can be applied to cases where it's not about a single team working on a single software product / project.
I also liked her explanations about various aspects of estimation: not everything she says will be easy / compatible with your environment or way of working, but those explanations will give you a good basis for thinking about, and later, managing your estimates.
Finally, as a minor criticism I have to add I wish the publisher / editor took more care to print graphs and charts in full color, instead of grayscale! Pragmatic Bookshelf should take such aspects of book quality more seriously. (