Management wants As-Is documentation for its existing application. It handles billions of dollars each month. And the developers have already started working on the Manufacturer side of the application and want a lot of code and reporting re-use. I'm with the Dealer side.
Coding starts in mid August.
How to get this done was the first meeting I attended after my company laptop was issued and I found my cube int he farm.
I suggested a light weight requirements process- a description of current functionality, a screen capture, a process flow activity diagram and functional descriptions we can infer from playing with the application. Once these "use cases" are complete, we'll walk SMEs through them to correct errors, add stuff we had no clue about and the like.
We will have the required baseline done in a very short period. Enough to do a Gaps Analysis of Version 1 compared to plans for Version 2.
So far we've created a "use case" number and title for each major major page and cross referenced to menus.
It seems to be working- at least the boss is very happy check marks in the tracker are increasing in quantity and the 'now published' announcement e-mails are coming a lot faster. The BA team has access to the QA/Development environment. I got the Create User doc done in about a day and a half. The current system, as you'd expect, has had several changes over the years and is, um, complicated.
Abstraction is a wonderful thing.
Since Create User is the first major design issue, I'm already talking about Version 2.0 with the IA/Designer as I delve deeper into this really cool piece of work that has combined two or three legacy applications and several upgrade security tools. This archeological stuff is interesting. The boss is a SME and quite amazing himself. So this isn't going to be the cluster ***k it could have been.
I'll letcha know. This Agile stuff works great. But of course, you and I already knew that.
Coding starts in mid August.
How to get this done was the first meeting I attended after my company laptop was issued and I found my cube int he farm.
I suggested a light weight requirements process- a description of current functionality, a screen capture, a process flow activity diagram and functional descriptions we can infer from playing with the application. Once these "use cases" are complete, we'll walk SMEs through them to correct errors, add stuff we had no clue about and the like.
We will have the required baseline done in a very short period. Enough to do a Gaps Analysis of Version 1 compared to plans for Version 2.
So far we've created a "use case" number and title for each major major page and cross referenced to menus.
It seems to be working- at least the boss is very happy check marks in the tracker are increasing in quantity and the 'now published' announcement e-mails are coming a lot faster. The BA team has access to the QA/Development environment. I got the Create User doc done in about a day and a half. The current system, as you'd expect, has had several changes over the years and is, um, complicated.
Abstraction is a wonderful thing.
Since Create User is the first major design issue, I'm already talking about Version 2.0 with the IA/Designer as I delve deeper into this really cool piece of work that has combined two or three legacy applications and several upgrade security tools. This archeological stuff is interesting. The boss is a SME and quite amazing himself. So this isn't going to be the cluster ***k it could have been.
I'll letcha know. This Agile stuff works great. But of course, you and I already knew that.
Posts
No comments:
Post a Comment