What Drives Quality: Toward a Second Edition
I'm updating and expanding my successful second book What Drives Quality. Intermediate versions are released through Leanpub: What Drives Quality.
I'm updating and expanding my successful second book What Drives Quality. Intermediate versions are released through Leanpub: What Drives Quality.
My 2nd book What Drives Quality has been officially released today (September 30). It is now available on Amazon and all other major bookstores.
CRAFT is about software craftsmanship, presenting which tools, methods, practices should be part of the toolbox of a modern developer and company, and serving as compass on new technologies, trends. You can learn from the best speakers and practitioners in our community.
This second post in the series on handling impediments builds on the process described in Handling Impediments: Why it Matters! I'll dive into the first step: recognizing the problem.
In this workshop you will learn how to scale agile retrospectives, doing them with multiple teams from a project, product or organization, practice facilitation skills with different retrospective exercises, and learn how you can introduce and improve retrospectives. You will also learn to do agile self-assessments and readiness checks and to design and facilitate retrospectives that help organizations to increase their agility.
People are often afraid to make mistakes. They do things to prevent that something might go wrong and avoid doing things that might fail. And if it does go wrong then they don't talk about it. Is it really bad if once in a while something goes wrong? If something can go wrong, let arrange for it to happen as soon as possible, because then you can quickly learn from it. Create a culture where failure is allowed so that we can all learn from it and find ways to make fewer mistakes!
Is het wel zo erg als er een keer iets fout gaat? Als het fout kan gaan, laat dat dan maar zo snel mogelijk gebeuren, want dan kun je er van leren. Creëer een cultuur waarin falen mag, samen op weg naar minder fouten!
Hoe doe je IT projecten binnen een vastgestelde tijd, budget en grootte, met een Agile aanpak, die wel gebruikersverhalen (user stories) en een planning (backlog) heeft, maar geen vaste scope en einddatum?
How can you manage projects with the agile approach, using user stories, planning games, and a flexible scope?
Do you use checklists in your daily work? Or do you hate checklists? what's your experience with them?
What kind of benefits can Agile teams bring for their projects, and how can you introduce agile teams into an existing project management organization?
Many books have been written about teams and team working – but very few pay attention to the needs of individual team members. The book "iTeam - Putting the "I" Back into Team" from William Perry does, and describes how you can build an effective team with individuals.