Seeding Visits | Glossary

Definition: 

Martin Fowler proposed the term “Seeding Visits”, one of the most popular approaches to getting together. He says, these should occur early in the project and are intended to create the relationships. A seeding visit that brings all team members together at the start of a project can be one of the best possible investments in the success of the project. This is important for projects on which team members do not know each other, have minimal shared history, distributed across the geography having different languages coming from different cultures.

This face-to-face kickoff gives an opportunity to meet each other, establish a rapport, and understand the project together.  One release cycle is beginning, the preceding one is ending. This is an ideal time to bring a team together. Teams can be colocated for the vision-setting and planning of the new release, for reviews and retrospective. Bringing the team back together for the last couple if iterations before the final release makes the process of shipping a final deliverable much smoother. Bringing the whole team together, helps in making key decisions. 

Further Reading:
Book: SUCCEEDING WITH AGILE Software Development Using Scrum by Mike Cohn

Interrupt-Driven Organisation | Glossary

Definition: 

Interrupt-Driven Organisation are like a hospital emergency room where changes are constantly popping up and the real focus becomes successfully triaging opportunities to ensure teams are always working on the most important items. Few organisations are in industries that change so rapidly that they cannot set priorities at the start of the sprint and leave them alone. Many organisations think they exist in that environment, which they are not. 

It is usually a matter of becoming accustomed to thinking ahead. There are multiple factors which triggers an interrupt such as change in market situations, regulations, policies which needs to be absorbed for competitive advantage.  If organisation is one from whom sudden, near constant change is a fact, it is better to consider using shorter sprint. 

Further Reading:
Book: SUCCEEDING WITH AGILE Software Development Using Scrum by Mike Cohn