Agile and Beyond 2017

Agile encourages us to eliminate activities that don't add value and find the simplest solution possible to solve our business needs. For many teams, that can lead to a state where collaborative design no longer happens or is discussed on a whiteboard that gets erased after the conversation. How then, can you share the knowledge with team members who don’t work on that component, or who join the team after the system is built?

I'll present a very simple method that can help everyone understand what the team plans to create or change in your current systems before it's built, that can also be retained to increase the domain knowledge for that system later.