Build It Like A Startup: Four Agile Practices That Create Innovation
1. Quick development cycles create urgency and accelerate learning for better products.
2. Customers are the measure of product accuracy.
3. A clear product vision guides organic product discovery.
4. Teams organized around product are more efficient than teams organized around function.
A product manager that extends quick development iterations out to the customer and centers the vision on their problems, keeps the process fast and lean, and gives your product time to innovate. Anyone challenged by the "we need to out-innovate the competition" battle cry will find help from these concrete practices.
Bio:
Greg Gehrich helped build a startup to a mid-size business of over 1000. In his roles as software development leader and product manager, he saw a strong contrast between the early entrepreneurial years and after they became more established. After he left that company and started hearing about how progressive startups were using agile and lean ideas, he was compelled to write a book that combined these current best product practices with his early startup experiences.

That was my first BayALN meeting in about 5 months. I have to say it was disappointing. Given the topic and title, I expected a lot more pizazz and jazz. Pretty much concur with most everything that has been said so far. In fact, I didn't even see any new groundbreaking ideas here. I(we) have been doing MVP for over the past year. But all that said, it was great to see a good turn out and know that BayALN is still alive and well! Thanks to David and Alicia and all other COCOs for getting it set up!
February 27
Unfortunately, the delivery was flat (no voice modulation), which made it difficult to stay engaged. AND Content was great and very useful and slides were some of the best (simple with VERY illustrative graphics). If the delivery was better, would add 1-2 additional stars.
February 27
I thought that the information is probably helpful, but the delivery was disjointed and unenthusiastic. I think that if some stories were included, even if they are huge failures, it would be much more engaging. How did the speaker discover his tenets? What led to the development of the flow. Discriptions of a few real life situations would peak everyone's interest.
A working session on the Business Model Canvas would be really helpful and intgeresting. The model looked very much like an A3. Is it similar? The speaker's manner, even if he is kind of even and non-excitable has to be energized. Although, I am sure the information passed on must be one of his passions, after all he's written a book and then extrapolated a presentation, it was communicated as if it didn't really matter, the audience could take it or leave it.
That all being said, I thought that there was much to consider.
2 · February 27
Great information,Greg. As already suggested, adding some related stories of agile vs non-agile situations could help with the entertainment aspect and generate audience interaction as well. For the "abnormal exit" topic, it seems to me that a verification step prior to the "communication" activity is needed that where the Product Leader collects specific data for reporting/communicating to the Product Owner. The communication activity would then also provide an ongoing review and governance of meeting requirements, quality, schedule, and MVP. An additional output from "Communication with the Product Owner" could be "abort" instead of adding to the backlog. I hope to get your slides.
February 27
Good message. One thought, could you spend the ENTIRE session on the Chart (the 1 slide) only? Its really good. You could explain how it works, each section, etc. Then take the group into a hands-on session to fill out their own. For example, ask them to pretend they are Melissa M - CEO of Yahoo! filling this out. How would they respond? Then do a read-out for some teams and regroup.
1. Explain the Chart
2. How each section works/ what to include
3. Provide an example (real life) of a Chart
4. EXERCISE: Each table does one together (see above)
5. Read out of some responses
6. Reflect and conclude
This would have made the session more interactive with one another b/c I think 90% of the attendees know Scrum & Kanban (don't need to explain it using his own definition). Focus - rather - on the key component. The chart slide made me want to know more.
That would be my counsel for the next go around...
Stacey Louie, Organizer
SiliconValley - Agile Leadership Network
February 27
the slide deck was extensive, yet the materials were a bit basic for me. I wonder if they were targeted to the audience appropriately. it would have been good to focus on innovation and the 4 practices, rather than the complete survey of what Agile and Lean meant to the presenter.
The presenter seemed a bit off of his game, reading the slides, and not interacting that much with the audience until the open Q&A in the end.
1 · February 27
some very good points in the presentation, but the style overall was deadly... needs more energy and interaction with audience. I really enjoyed audience discussion at the end of the presentation, very good involvement
February 27
Hi - I believe a session with the MVP worksheet and some different business case studies would have been relevant. Would suggest to break this into groups of 4-5 members each and make a hands on session as Stacey suggests. I did think the other slides were confusing and not clear.
1 · February 27
Some real pearls that will shine with a few more "Agile sprints iterations", good first MVP. Keep going Greg!
February 27
This looks like a really exciting discussion on how to startup businesses rapidly using agile techniques. Looking forward to it and bringing a bud :)
February 26
Join or login to comment.