Reformulating the Product Delivery Process
Israel Gat, Erik Huddleston and Stephen Chin present how Inovis realized a higher product throughput by using three unconventional Kanban practices and a Lean Release Management tool called APROPOS.
Tracking change and innovation in the enterprise software development community
Posted by bor!sgloger on Aug 11, 2010

Scrum is a framework with simple rules. This Scrum Checklist will help you to remember these simple rules in the heat of daily work and stress. It enable you to create an enjoyable and productive work environment with your Scrum-Team.
For Scrum Beginners - Follow the Checklists, do Scrum by the book.This will enable you to run you first 3 to 4 Sprints very successfully. Your success will facilitate to spread Scrum in your organization.
For Scrum Intermediates - Use your common sense to tweak your processes guided by these Scrum Checklists.
As an experienced ScrumMaster - Use Scrum Check- lists as your safety belt in stressful situations.
Scrum Checklists do not replace experience and practice. Scrum Checklists are not procedures that you have to follow. Scrum Checklists help to run a successful Scrum in a demanding environment.
24 pages booklet, Publisher: bor!sgloger Wien. New York. Recife. Baden-Baden. ISBN-13: 978-3000282010
Courtesy of Boris Gloger, we're happy to offer the free nonprintable copy for download, to get this knowledge in as many peoples hands as possible. Login to Login to download this book FREE (PDF)
If you enjoyed reading the free (non-printable) download version, please support the author by buying the print version. Order it directly via email at office@borisgloger.com for 9,99€ incl. VAT + shipping costs or order it from your bookstore using the ISBN-13: 978-3000282010.
Over 5000 people trained in Scrum. 3000+ certified. Companies consulted in Germany, Austria, Switzerland, Finland, Denmark, England, Poland, South Africa, Brazil, the USA, and China. Teams, departments and whole companies made more effective. Boris Gloger, student of Ken Schwaber, inventor of Scrum, consults customers and teaches Scrum to develop their products more efficiently, faster, and reliably since 2003. He has had his fare share in making Scrum the de facto standard of agile software development in Europe, South Africa, and Brazil.
Boris Gloger is the No. 1 in Europe concerning Scrum in a company. He has successfully implemented Scrum in companies alone as well as together with his Scrum implementing teams, educated trainers in Germany, taught coaches how to use Scrum with teams, and in our opinion he has developed the most successful variant available for implementing Scrum. Furthermore he had a major impact on developing Scrum generally: The retrospective for instance is one of his influences. He also developed the Scrum Checklist, which is used worldwide, that helps teams to work with teams quickly. Boris has influenced and worked together with other important Scrum people like Ken Schwaber, Norman Kerth, Jeff Sutherland, Tobias Mayer, Jens Östergaard and many, many trainers and consultants. He is always ready to share his knowledge with his consultants, with thousands of participants of his trainings, and the readers of his blog www.borisgloger.com and books.
ScrumCore Training. Certified ScrumMaster and Certified Product Owner public and private courses
A ScrumMaster’s Checklist: Product Owner, Team, Dev Practices, Organizational
ScrumWorks Pro is the only Scrum project management tool designed for the enterprise. Sign up for a free 35-day trial.
Israel Gat, Erik Huddleston and Stephen Chin present how Inovis realized a higher product throughput by using three unconventional Kanban practices and a Lean Release Management tool called APROPOS.
Ross Mason discusses how to use enterprise mashups by applying a number of patterns, such as FeedFactory, Super Search, and Pipeline, in order to find new ways to benefit from existing enterprise data
Udi Dahan discusses the Command Query Responsibility Segregation (CQRS) pattern, detailing on queries and commands, what they are and how they should be used in an asynchronous programming environment
Olivier Mallassi shares a story of a typical software development project, some typical problems and what he learned from Tom Demarco about addressing those problems, and an alternative story.
Ralph Johnson discusses principles, practices and tools relating to software development starting from already existing code which needs refactoring, maintenance, and sometimes architectural change.
At a recent IIBA New Zealand members event Shane and Pete debated the role of the business analyst on Agile projects. They looked at the importance of analysis on projects and how the role changes.
Pete Goodliffe provokes his listeners to keep learning, offering advice on how to approach learning, what is valuable and what can be ignored, how to deal with new things, having a healthy attitude.
If you want a job in Agile software development, using a framework like Scrum, you need a plan of action that spans all three phases of your job search: preparation, interviewing, and assessment.