Re: SIP is not Takt Time
| Newsgroups | gmane.comp.programming.software-in-process |
|---|---|
| Message-ID | <[email protected]> |
--- In [email protected], Dossy <dossy@p...> wrote: > From a business perspective, they're looking for the cycle time of > the entire story, which they might call "lead time" to having the > feature implemented/deployed -- which will include the cycle time > for the programming team's work, as well as the cycle time for the > business Customer to specify the story itself, as well as any > auxillary testingor documentation cycles that must be carried out > if necessary. The entire process would be the lead time for the > feature ... and I think SIP should be the measure of that lead > time. I stand corrected, I agree with you completely on this. The 'duration' in question is the time from when a story is needed by the business until they get the story implemented. That duration is - well - I still do not like the term *lead time*. It does not seem to me to carry the same meaning in production and inventory control, and I figure once a word has two meanings it's useless. We can call it SIP or I will call it service time. But in any event, I definately include time for the customer to formualte the story as part of this time. Mary ------------------------ Yahoo! Groups Sponsor ---------------------~--> Get 128 Bit SSL Encryption! http://us.click.yahoo.com/LIgTpC/vN2EAA/xGHJAA/NhFolB/TM ---------------------------------------------------------------------~-> To unsubscribe from this group, send an email to: [email protected] Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/