View source for Proposal - education curriculum and operation

= For Developers & all Technology Managers (including CTOs) =


<br>
<br>
==== LASD1 (Lean & Agile Sw Dev 1): Readings ====

Summary: Readings

Person-hours: 5-10

Content:
 Chapter: Systems Thinking. Book: Scaling Lean & Agile Development.
 Chapter: Lean Thinking. Book: Scaling Lean & Agile Development. OR... the online Lean Primer @ http://leanprimer.com/
 Chapter: Be Agile. Book: Scaling Lean & Agile Development
 The New Methodology @ http://www.martinfowler.com/articles/newMethodology.html
 Agile Values & Principles @ http://agilemanifesto.org/
 Scrum Guide @ https://www.scrum.org/Scrum-Guides
 Scrum Primer @ http://scrumprimer.org/
 Unit TDD @ http://www.jamesshore.com/Agile-Book/test_driven_development.html
 Refactoring @ http://www.jamesshore.com/Agile-Book/refactoring.html AND http://www.refactoring.com/catalog/index.html
 Chapter: Test. Book: Practices for Scaling Lean & Agile Development
 Chapter: Continuous Integration. Book: Practices for Scaling Lean & Agile Development
<br>
<br>

==== LASD2: Course: Agile Software Development: Hands-On Practices, Principles, Agile Modeling, And TDD ==== 

Content Summary: Core hands-on skills in agile sw development/engineering (unit TDD with refactoring, acceptance TDD, continuous integration, clean code, agile modeling for user experience, analysis, and design), and solid OO design

Experience Summary: In this extremely hands-on course, 2 teams (e.g., 14-16 people), each working together as a team, learn and apply in a structured environment with a carefully crafted education system and set of problems. The coach works intensively with the teams during group agile modeling, and intensively with the programming pairs, during development.

Duration: 5 days. 

Detailed Description: [http://www.craiglarman.com/wiki/index.php?title=Agile_Software_Development:_Hands-on_Practices,_Principles,_Agile_Modeling,_and_TDD Agile Software Development: Hands-On Practices, Principles, Agile Modeling, And TDD]

Special Readings for Future LASD Teachers:
* Applying UML and Patterns 3E, Larman: Chapters 1-25
* Clean Code, Martin: Chapters 1-10
* User-Centered Design, Lowdermilk, All chapters (it's a short book - a solid overview of basics)
<br>
<br>

==== 2+ week break  ====
<br>
<br>
==== LASD3: Workshop: Core skills applied in a mini-Sprint with a work goal ==== 

Context: It is helpful to learn & apply new complex skills in a structured classroom environment, but to go from "knowing to doing" in the ''workroom'' requires a critical extra step.

Content Summary: The skills of LASD2 are applied to a company goal, that the teams and company mgmt pick (vetted by the coach), in a 5-day mini-Sprint

Experience Summary: The 2 teams, each working together as a team, are led through a mini-Sprint. The coach works intensively with the teams during group agile modeling, and intensively with the programming pairs, during development, introducing new principles and practices and design patterns as situationally appropriate.

Duration: 5 days. 

Environment & Tools: Same as LASD2, but definitely access to your real development (source code, .etc) environment, as we are building "real" software.
<br>
<br>

==== 2+ week break  ====
<br>
<br>
==== LASD4: Clinic: Legacy-Code TDD ==== 

Context: It's easy to create clean code and do TDD and refactoring in a green-field context (LASD2 and LASD3), but that's not the reality of the developers and the legacy code base. The craft of ''legacy-code TDD'' is a ''very'' different and challenging skill-set and requires distinct coaching, in the context of your real existing legacy code. Especially difficult is breaking dependencies in the existing code, to enable for TDD, and this requires very situational coaching.

Content Summary: Legacy-code TDD and refactoring, breaking dependencies.

Experience Summary: 1 team does a "coding dojo" style learning with the coach. The team and coach are surrounding a projector displaying the legacy code, and for a 10-minute cycle, one person does legacy-code TDD and refactoring and dependency breaking, guided by the coach. Then "driving" the keyboard rotates to the next team member, etc.

Duration: 2.5 days. 

Note: The coach will complete team 1 and team 2 coaching over a 5-day period.

[http://www.craiglarman.com/wiki/index.php?title=Consulting_and_Education#Hands-on_Coaching:_Legacy_Code_-_Breaking_Dependencies_and_TDD_.28C.2C_C.2B.2B.2C_C.23.2C_Java.2C_Python_....29 See further description here]
<br>
<br>

==== 2+ week break  ====
<br>
<br>
==== LASD5: Course: Agile Design And Modeling For Advanced Object Design With Patterns ==== 

Content Summary: Hands-on skill and mastery of excellent and flexible software design with design patterns; more agile modeling skill.

Experience Summary: As in LASD2, in this extremely hands-on course, 2 teams (e.g., 14-16 people), each working together as a team, learn and apply in a structured environment with a carefully crafted education system and set of problems. The coach works intensively with the teams during group agile modeling.

Duration: 3 days. 

Detailed Description: [http://www.craiglarman.com/wiki/index.php?title=Agile_Design_and_Modeling_for_Advanced_Object_Design_with_Patterns Agile Design And Modeling For Advanced Object Design With Patterns]

Special Readings for Future LASD Teachers:
* Applying UML and Patterns 3E, Larman, Chapters 26 and 36
* Head First Design Patterns, or the original Design Patterns
<br>
<br>
<br>
<br>

==== no break (start next event on subsequent day)  ====
<br>
<br>
==== LASD6: Workshop: Agile Architecture Documentation Workshop ==== 
Summary: There is a large system and the overarching existing design is not clear to many. This also inhibits evolving the design for the future. In this 1 day workshop, the coach facilitates the group to create architectural views and technical memos in a highly collaborative hands-on workshop using vast whiteboard spaces, to sketch out the existing product architecture, and also capturing Q&A sessions on video. The output is not only the many architectural view sketches (logical, process, data, deployment, security, ...) and technical memos, but a shared understandings amongst workshop participants in the existing design, using lightweight and fun methods that transform "documenting the architecture" from a boring low-value activity into an interesting high-learning high-value event.
This workshop can also be combined with the definition and organization of a self-study plus Q&A mentoring system for new hires to your company, to speed and improve the architectural knowledge of your staff.

Duration: 1 day. 

Detailed Description: [[Agile Architecture Documentation Workshop]]

Special Readings for Future LASD Teachers:
* Applying UML and Patterns 3E, Larman, Chapter 39

<br>
<br>
==== LASD7: Architecture 2.0 ==== 
Summary: Exploring JPM Architecture 2.0, using Agile Architecture Documentation Workshop techniques.

Duration: 1 day. 

Environment: Same as LASD6
<br>
<br>

=== Adoption & Operating Model ===
To scale this, I recommend that an internal cadre of ''technical coaches'' (such as existing managers and architects) become certified to deliver this. The programme will start with some existing certified external coaches (e.g., craig, ...) that deliver this programme, with participants who will in the future deliver it separately. 

Each potential coach must attend the cycle of education ''twice'', before certification.

To aid in the coach-certification and learning process, the original deliveries by external expert coaches may be video-recorded (but only used for coach preparation). 

I recommend that virtually all teams within the organization go thru this education process.
<br>
<br>
<br>
<br>
= For Tech and Business Managers =
<br>
<br>
==== LAM1 (Lean & Agile Mgmt 1): Readings ====

Summary: Readings (some free and online, some are digital or paper books) 

Person-hours: 10-20 hours

Content:
 Systems Thinking
 Lean Thinking
 The New Methodology
 Agile Values & Principles
 Scrum Guide
 Scrum Primer
 [http://www.craiglarman.com/wiki/index.php?title=Readings#Pre-readings_for_Management_Teams Other Readings for Managers]
 ??? Possibly also selected chapters from "Out of the Crisis" [Deming]
<br>
<br>
==== LAM2: Course: Scrum and Lean Thinking ==== 

Summary: Essentially, the 2-day course i have delivered at the organization a few times now.

Duration: 2 days. 
<br>
<br>
==== no break (start next event on subsequent day)  ====
<br>
<br>
==== LAM3: Course: Special Topics: Large-Scale Scrum, Impact Management, ??? ==== 

Details to be decided.

Duration: 1 day. 
<br>
<br>
==== no break (start next event on subsequent day)  ====
<br>
<br>
==== LAM4: Clinic: Deep-dive Q&A ==== 

Duration: 1 day. 
<br>
<br>
[[Deep-Dive Question And Answer Management Workshop - Lean/Agile Product Development]]
<br>
<br>
<br>
<br>
= For Future Product Owners =

First, the education in the [http://www.craiglarman.com/wiki/index.php?title=Proposal_-_education_curriculum_and_operation#For_Tech_and_Business_Managers For Tech and Business Managers] section above.
<br>
<br>
==== PO1 (Product Owner 1): Readings ====

Summary: Readings (some free and online, some are digital or paper books) 

Person-hours: 5-10 hours

Content:
 to be decided
<br>
<br>
==== PO2: Course: Certified Scrum Product Owner ==== 

Details: [[Certified Scrum Product Owner Course]]

Duration: 2 days. 
<br>
<br>
==== no break (start next event on subsequent day)  ====
<br>
<br>
==== PO3: Clinic: Deep-dive Q&A ==== 

Duration: 1 day. 
<br>
<br>
[[Deep-Dive Question And Answer Management Workshop - Lean/Agile Product Development]]