Download - Agile study group
Taylor Weber
Everything we are doing as faculty, the entire structure of this institution and system, is based on the thinking of these men
Old NewTeaching them an assortment of foundational theory and functional skills (programming, networking, security) is sufficient
They need to understand the flow of the collaborative product design process through a system of value
Companies vary too greatly in how they employ our graduates for academic training to cover practical issues
There is an emerging empirical consensus around how this is most effectively done. (See: Silicon Valley, Seattle.)
Product design is not our field IT is an increasing component of products in general and this requires particular skills
Industry partnerships are essential
Yes, but we need to have a backup plan & strategy when they are scarce
Old New
Theory is relevant for core computer science, but not industry practice
There are relevant theories that WE as educators should be using to inform our pedagogy
Agile is a cultural and generational phenomenon
Agile has sound empirical and theoretical foundations
Technology is moving too fast (and HOW on earth can we keep up?)
There is a high value, stable pedagogical core we can identify
Engineering Design
What’s missingAgile, Lean, Devops, Scrum, Kanban, product & service design, collaboration, flow, lean startup (test/learn/pivot), automation, complex adaptive systems, Cynefin, intersection of ops mgmt & IT,
Pitch: Agile study group
MN educators (MNSCU, ACTC, U of MN, etc)A supported, formalized, time-boxed collaborative effort to explore & develop these concepts for the benefit of Minnesota high technology educationWhat does this mean? I don’t know. Can we talk?
Charlie’s 2 current projects: - Calavera simulation (part of insanIT)- 3rd edition of Architecture of IT Management
Theory Pedagogy Delivery
The starting books