Comments on: 4 – Models http://shipitontheside.com/2008/12/4-models/ The podcast about building a Software Startup as a side job. Tue, 04 May 2010 08:31:02 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: John Burns http://shipitontheside.com/2008/12/4-models/comment-page-1/#comment-17 John Burns Sun, 04 Jan 2009 19:32:00 +0000 http://shipitontheside.com/?p=40#comment-17 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. 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.

]]> By: Martin L. Shoemaker http://shipitontheside.com/2008/12/4-models/comment-page-1/#comment-15 Martin L. Shoemaker Tue, 30 Dec 2008 21:21:47 +0000 http://shipitontheside.com/?p=40#comment-15 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! 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!

]]> By: Michael Eaton http://shipitontheside.com/2008/12/4-models/comment-page-1/#comment-14 Michael Eaton Sat, 20 Dec 2008 16:45:10 +0000 http://shipitontheside.com/?p=40#comment-14 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! 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!

]]> By: Mis Speller http://shipitontheside.com/2008/12/4-models/comment-page-1/#comment-13 Mis Speller Thu, 18 Dec 2008 19:07:07 +0000 http://shipitontheside.com/?p=40#comment-13 Browable Flowerpot Software Model (overview) Browable Flowerpot Software Model (overview)

]]>