Extreme Manufacturing in 5 Minutes

facebooktwittergoogle_plusredditpinterestlinkedintumblrmailfacebooktwittergoogle_plusredditpinterestlinkedintumblrmail

I recently gave a presentation to the Pacific Northwest Orginizational Development Network (PNODN). I had 90 minutes total, 10 times as many as TEDxRainier, and was able to dive deeper into Agile, Lean, Scrum, Kanban, and XP practices applied together for manufacturing and R&D. I called using all of these together “Extreme Manufacturing”, or “XM” for short, to thank Kent Beck for his visionary work with Extreme Programming. As a challenge for myself and an opportunity to learn a lot about sharing what I’m leanring with WIKISPEED, I attempted to get 5 volunteers from the conference attendees to be useing XM in 5 short minutes. I’ll update this blog post with a link to the video as soon as I have it back from the PNODN event organizers and have posted it to the WIKISPEED YouTube channel. Here are the 5 steps we went through together, accompanied by some coaching and, in the case of the first step, some very quick guided meditation/visioning:

 

Step 1: Become a Product Owner in 1 minute.

SUCCESS CRITERIA: You have a clear vision of a product or a project that gives you a warm fuzzy feeling deep in your tummy.

 

Step 2: Write 1 or more User Stories in 1 minute.

SUCCESS CRITERIA: you have written your vision formatted like: “AS someone I CAN do something SO THAT I experience a value that gives the Product Owner a warm-fuzzy feeling.”

 

Step 3: Write Acceptance Tests per User Story in 1 minute.

SUCCESS CRITERIA: Write down the simplest, quickest way to know your user gets the value, and give you that warm-fuzzy, in each of your User Stories. Maybe “I’ll ask my neighbor to try a mock-up of my product and film their reaction.”

 

Step 4: Write Tasks for each User Story in 1 minute.

SUCCESS CRITERIA: One or more actionable tasks to help make each user story come true. Things like “Plant 3 native trees” and “build a birdhouse”.

 

Step 5:  Prioritize The User Stories.

SUCCESS CRITERIA: You have a column of your user stories, with the stories that give the most value to your user on top. Look for dependencies, if one story must come before another see if you can throw that story out or re-write it.

 

Step 6:  Schedule your Demo of The User Stories.

SUCCESS CRITERIA: Your have a calendar item in your phone for a 1 hour block to execute each test to determine which stories are done. A 5 minute block can work if you need to.

 

Step 7:  Schedule your Work Time on The User Stories.

SUCCESS CRITERIA: Your have a calendar item in your phone for a 1 hour block, days before the demo, to complete tasks. Hopefully with a pair, or better yet a team of pairs, to whom you will clearly articulate your vision.

And that was it! This was all framed in the rest of the 90 minute session, but I’d be very interested in if these 7 steps can come even close to standing on their own and delivering value to anyone. I’m alsways fascinated in trying to share the best I understand to date in the shortest amount of time responsible, so that folks can get right to using the parts of it that might translate to their work.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>