meta user
network profile
| bio | website | thinkboard.wordpress.com |
|---|---|---|
| location | Frankfort, KY | |
| age | 45 | |
| visits | member for | 1 year |
| seen | 2 days ago | |
| stats | profile views | 37 |
Software developer since 1992. Programming since 1989. C, Centura Team Developer, SQL, VB.Net, C#, ASP.NET. Learning Objective-C. MSCS 2010 Kentucky State University. Only one app in the App Store.
|
Apr 24 |
comment |
How do tight timelines and scheduling pressure affect TCO and delivery time? Steve McConnell enumarates "Overly optimistic schedules" as one of the classic software development practice mistakes, and a major source of project problems; this would be the cause of scheduling overruns in the first place. stevemcconnell.com/rdenum.htm |
|
Mar 18 |
comment |
What can be used in lieu of use cases to gather requirements? I was trying to find a substitution for the 'use case' part, not for the whole user requirements document. The reference in John Niedzwiecki's answer to 'user stories' seems pretty good and it could face less resistance than 'use cases'. |
|
Mar 18 |
comment |
What can be used in lieu of use cases to gather requirements? We create what we call User Requirements Documents (URDs) with the typical long narrative; we separate out requirements into sections, including business need, scope, time frame, some design specifications as well as screen shots where appropriate; never included 'use cases'. Our URDs might not be correct technically speaking but, have been good and have worked out fine in many instances; and we are going to create another URD again. However, it was pretty obvious that including 'use cases' this time would be very helpful, only to face unexpected answer the BA not liking use cases. |
|
Mar 15 |
comment |
What can be used in lieu of use cases to gather requirements? Good questions which, I did not ask but will ask next time we meet. |
|
Mar 15 |
awarded | Student |
|
Mar 15 |
asked | What can be used in lieu of use cases to gather requirements? |
|
Oct 8 |
awarded | Teacher |
|
Sep 16 |
comment |
How can I quantify the amount of technical debt that exists in a project? @ErikDietrich I would suggest to put that "kind of number" to indicate cost in the following manner: because our code base is 'this bad' it is taking 'this long' to implement 'this change', consecuently our 'time to market' (or time to delivery) is 'this'. 'this bad' would be your code metric, whichever is best for your particular needs, 'this long' would be, and this is my suggestion, your technical debt cost because you could put numbers on it as time and money; if implementation effort takes 'this long' and dev rate is $/hour, you could find out how long and how much the changes cost. |
|
Sep 1 |
awarded | Supporter |
|
Aug 25 |
awarded | Editor |
|
Aug 25 |
revised |
What is an “implementation plan”? added a link reference to a check list |
|
Aug 25 |
answered | What is an “implementation plan”? |
|
Apr 28 |
awarded | Autobiographer |
