I will provide a quick overview of how an Abstract Visual Modeller works. There are a few of us around the globe, I will be referring to others from time to time. I till be concentrating on 3 key issues:
- How we represent development process,
- How we cut through "analysis paralysis" and discover things customers didn't know they wanted,
- How we derive abstractions
After that intro (very condensed), we will run a brainstorm on (1) how existing Visual Modelling techniques can benefit Kanban/Lean, and (2) how limiting WIP can be applied to Visual Modelling practices.
Comments