#novsm: understanding and mapping your knowledge discovery process
DESCRIPTION
Presented as a short talk at Lean Kanban North America 2014 conference in San Francisco on May 7, 2014. Sorry, the words actually said during the talk and the words on the slides don't have much overlap. This is by design. I don't want to be seen reading slides even if I have memorized them. As I understand, attendees will get the video.TRANSCRIPT
- 1. #NoVSM: Understanding and Mapping Your Knowledge Discovery Process Alexei Zheglov #lkna14 @az1 yet another provocative #NoHashtag
2. Why are we here?... ...We want beautiful organizations. ~ Frode Odegard 3. Understanding? BA Dev Test Deploy 4. Visualize? BA Dev QA Deploy DoneBacklog 5. Just Add WIP Limits? BA (2) Dev (3) QA (2) Deploy DoneBacklog ? ? ? 6. Is There a Better Way? Toyotas Product Development System is completely different from the Toyota Production System. ~ Michael Kennedy Hints: knowledge discovery, information arrival 7. Knowledge Created (not necessarily in this order) Exact production environment configuration (OS, Web server, DB server, third-party software, etc.) Key behaviour examples (acceptance criteria, executable specs, use cases, etc.) Integration (upgrade procedures, data migration, etc.) Code design and implementation Tests needed to support the code Actual behaviour of the integrated software WRT non-functional requirements Results of usability tests and exploratory testing sessions Etc. 8. Knowledge Accumulated Time KnowledgeAmount Specification by Example Code Construction Exploratory Testing Deployment 9. Knowledge Accumulated Time KnowledgeAmount Dominant Activity #1 Dominant Activity #2 Dominant Activity #3 #4 Not handoffs Changes in the dominant activity Shifts in the collaboration pattern 10. Example #2 (Lean Startup circa 2003)KnowledgeAmount Time establishing baseline measuring improvement client validation engineering/DevOps advertising campaign managers creative staff sales 11. Example #3 (Courseware)KnowledgeAmount Time fact finding instructional design drafting beta-testing publishing 12. Mapping. Why? Activity 1 Activity 2 Activity 3 KnowledgeAmount Time 13. Mapping. Why? DoneBacklog Activity 1Input Queue Output Buffer ??? Activity 2 Activity 3 ? 14. Before We Begin... System Model Creating the Model Youre here 15. Before We Begin... System Improvement Model/Map Provoke improvement, not inertia 16. Assumption: Services Group What? To Whom? Why? fitness criteria expectations arrival patterns Service 1 Service 2 Service 3 Service 4 17. Repeat for Every Service DoneBacklog Activity 1Input Queue Output Buffer ??? Activity 2 Activity 3 ? Service 1 All Other Services 18. Respect Complexity Emergent: Dominant activities Turning points Explicit policies Start with examples 19. Invite Everyone 20. Things on the Left, Things on the Right Knowledge discovery Dominant activities Collaboration Models affect systems Linearized Flow Process fits brains Improvement Need an acronym Assembly Functional silos Handoffs Models reflect systems Backflows SharePoint Inertia VSM 21. References Kurtz, Cynthia F., and Dave Snowden. The New Dynamics of Strategy: Sense- making in the complex-complicated world. (2003) Kennedy, Michael N. Product Development for the Lean Enterprise (2010) Cynefin diagram, CC-BY 3.0: http://en.wikipedia.org/wiki/File:Cynefin_framework_Feb_2011.jpeg Anderson, David J. Understanding the Process of Knowledge Discovery. http://djaa.com/understanding-process-knowledge-discovery (2011) Zheglov, Alexei. Kanban and Lean Startup, Making the Most of Both. http://www.agileconnection.com/article/kanban-and-lean-startup-making-most- both (2012) Zheglov, Alexei. Understanding Your Process as Collaborative Knowledge Discovery. http://connected-knowledge.com/2014/04/19/understanding-kdp/ (2014) Thank You! Alexei Zheglov @az1 [email protected] Blog: connected-knowledge.com