4 Comment(s)

1. Browable Flowerpot Software Model (overview)

   Mis Speller | Dec 18, 2008 | Reply

2. W00t! Thanks for the shoutout Martin!

   The client you mentioned near the end of the podcast actually created an NDA that covers peer review for my friends and colleagues to sign. Over the past few weeks, I’ve had some very smart people jump into code reviews using Microsoft SharedView and it’s been absolutey fantastic!

   Michael Eaton | Dec 20, 2008 | Reply

3. Thanks for the update, Mike! I’m hoping yours will be a pioneering effort, and some day I’m seeing you give a conference talk on how to do buddy reviews right. Heck, over time you may parlay that into a book!

   Martin L. Shoemaker | Dec 30, 2008 | Reply

4. Thanks for the recognition. Hi Curtis…

   Six Use Cases:
   -1- Define offering – service or product
   -2- Identify Prospect
   -3- Qualify Prospect
   -4- Building Interest
   -5- Make Proposal
   -6- Closing the Sale

   An Aside… RE: “guys writing software”… there are also “girls”. This opens a big can of worms – kind of like the Software Engineer argument.

   Link on website for the model? not a link, yet. I would like to view so I can “ask some questions”

   #1 rule – Electronic tool – never drawing pretty pictures. Always a model.

   Maintenance, updating, developers – Use Cases – should be first.

   When is design of the tool/application/project done and time to write code. Nice way to define this (e.g. when team says it is, and unanimous decision to move ahead).

   Curtis: Off podcast… get well – we all want to keep listening.

   Martin: Off podcast… any plans for the UML Training – like you did last year at Air Zoo?

   Scott: Off podcast… cheers – must have been fun to “see the action” – even as you were working in the background.

   John Burns | Jan 4, 2009 | Reply

Post a Comment