% basePath=Application("sHttpPath") %>
The Agile Manifesto states that we value Individuals and Integration over processes and tools and Working Solutions over documentation.
So instead of spending hours, days and even weeks building elaborate Gantt Charts, Entity Relationship diagrams, Flow Charts, Data Flow diagrams and Project Management Plans, we have time-boxed events with a maximum duration.
Pre-described events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum.
Without the events, we are back to Plans and Models or vanity reports, which really don’t align with my favorite principle of the 12 principles in the Agile Manifesto: “Simplicity - the art of maximizing the amount of work not done is essential.”
This white paper will discuss the purpose and processes of each Agile Scrum event, and help you understand why they are so important.
Keith Wilson is a Senior Consultant and Trainer with IIL. His background includes over 25 years of successful coaching, training, management, and consulting experience. He is well known for his public speaking skills and enthusiasm and has been a welcomed facilitator at numerous Fortune 500 corporations, universities, and associations worldwide.