build a usable process, get buy in and enforce it

Post #51,656 by boxley 9/13/02 12:40:03 PM Reply	build a usable process, get buy in and enforce it The following stuff needs to be done and signed off on each step Needs requirement High level design document (detailed enough so coder is filling in blanks) coding with sccs of some kind coder doesnt release to test until personally satisfied test (regressive if possible) qa production With parallel efforts and resources the above should help identify the choke points. thanx, bill will work for cash and other incentives [link\|http://home.tampabay.rr.com/boxley/Resume.html\|skill set] [link\|http://home.tampabay.rr.com/boxley/index.html\|boxley's home page] qui mori didicit servire dedidicit
Post #51,660 by drewk 9/13/02 1:42:12 PM Reply	How do you do that in a small shop? It's hard to define a five-step process when there are only five people in the shop. I'm not just nay-saying, I actually want to know how to do a multi-stage formal process with <10 people. === Microsoft offers them the one thing most business people will pay any price for - the ability to say "we had no choice - everyone's doing it that way." -- [link\|http://z.iwethey.org/forums/render/content/show?contentid=38978\|Andrew Grygus]
Post #51,669 by boxley 9/13/02 3:36:35 PM Reply	one person might do all 5 it is scalable up and down. Userdefs, write a high level design that shows the methodology to achive the goal. Fill in the blanks, test it with a script or a tool deploy it to production. The idea is to document what you are doing so if someone follows behind you they can see the thought process that got you to where you are. thanx, bill will work for cash and other incentives [link\|http://home.tampabay.rr.com/boxley/Resume.html\|skill set] [link\|http://home.tampabay.rr.com/boxley/index.html\|boxley's home page] qui mori didicit servire dedidicit
Post #51,675 by drewk 9/13/02 4:00:58 PM Reply	Probably I guess having to have everything done yesterday is going to cause problems no matter what your procedures. Have I mentioned we are in the process of migrating off of an HP3000-based system? And that the 3000's only allow a 6-digit ordernum? And that we're currently at 934467? And that we're creating orders at the rate of ~500-600/day? How long does that give us to finish rebuilding the system? (A: About 4 months.) === Microsoft offers them the one thing most business people will pay any price for - the ability to say "we had no choice - everyone's doing it that way." -- [link\|http://z.iwethey.org/forums/render/content/show?contentid=38978\|Andrew Grygus]
Post #51,687 by boxley 9/13/02 6:18:37 PM Reply	well you could ]:-> assuming that the 1st orders were taken a long time ago setnext ordernum=100 takes about 3 seconds and gives you some time to breath. thanx, bill will work for cash and other incentives [link\|http://home.tampabay.rr.com/boxley/Resume.html\|skill set] [link\|http://home.tampabay.rr.com/boxley/index.html\|boxley's home page] qui mori didicit servire dedidicit
Post #51,885 by drewk 9/16/02 10:21:56 AM Reply	Like we haven't thought of that Every order we've ever done is still live in both the operations and accounting databases. Have to be able to look up all account history for any customer at any time. So no, we can't recycle early numbers. === Microsoft offers them the one thing most business people will pay any price for - the ability to say "we had no choice - everyone's doing it that way." -- [link\|http://z.iwethey.org/forums/render/content/show?contentid=38978\|Andrew Grygus]
Post #51,899 by boxley 9/16/02 11:49:00 AM Reply	you mean you couldnt archive 1-5000 into an identical sysytem with a query the grabs order 101 from the archive and makes it 101A on the user screen and in any sets doing totals would differentiate from the "new" 101. I am sure you have all worked on this. What kind of DB is it? thanx, bill will work for cash and other incentives [link\|http://home.tampabay.rr.com/boxley/resume/Resume.html\|skill set] qui mori didicit servire dedidicit
Post #51,911 by drewk 9/16/02 1:36:50 PM Reply	Too many things would have to change Every table that deals with order info uses ordernum as the foreign key. Every page that queries any of these tables would have to incorporate logic that says, "if it's less than 5000 then call it 5000a, unless you really mean 5000." And that would only buy us another couple of weeks anyway. Testing alone for the changes would take longer than that. And that doesn't account for the fact that until we are completely off of the old system everything we do has to migrate to and from that system. Which is maintained by a contractor on an as-needed basis. Any attempts to re-use low numbers amounts to trying to crash your plane in a valley instead of on a peak because you'll have a little while longer before you hit the ground. This plane is running on fumes, and we have to switch to the new plane before it hits the ground. === Microsoft offers them the one thing most business people will pay any price for - the ability to say "we had no choice - everyone's doing it that way." -- [link\|http://z.iwethey.org/forums/render/content/show?contentid=38978\|Andrew Grygus]

Welcome to IWETHEY!