aspose file tools*
The moose likes Agile and Other Processes and the fly likes Progress on Process Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Progress on Process" Watch "Progress on Process" New topic
Author

Progress on Process

Michael D. Brown
Greenhorn

Joined: Nov 22, 2003
Posts: 29
To give everyone an update, I have been hired as Director of Systems Development at a growing company. My first task was to direct a group of consultants as the team reengineers our core web application.
Using the input and research from my earlier question on which process to use for projects, I decided to use the Unified Process for this project. So in essence we are implementing the UP in conjunction with this project.
I have to admit that using UP has helped me get a handle on the system much faster than I could have by attempting to divine it by normal means. We spent a week walking through the system creating a Use Case diagram and workflow diagrams for a few of the Use Cases. I have taken those diagrams and created a full Use Case document from them. We were able to define nine packages for the system, which pretty much will translate into the subsystems for the application.
We have completed the Inception Phase and are three days away from finishing our first Elaboration iteration. Construction will begin on Monday after we have finished reviewing the first Software Requirements Specificiation (for the initial system prototype) that I am assembling now.
If you want proof that the Unified Process can be agile look no further than my example. I started at the company at the end of January (the 26th to be exact). By spending my first week in requirements gathering sessions, I was able to quickly come up to speed on the project. In three weeks time we have completed roughly 75% of the Use Case model (I estimate that about 25% of the completed model will be discovered as we go through the iterations) and detailed Use Cases for our first iteration. The initial project plan has been estimated for the first two iterations and the target for getting a working initial build is March 10th (roughly 5 weeks after the project started).
In the meanwhile, we just received our testing tools (Quicktest Pro and Test Director by Mercury Interactive). The development environment is configured and C&C Management is setup. Of course, none of this would have been possible without the right people. My boss (the CEO) decided to budget the money to have a good consulting firm work on this project before I was hired. They were able to drive the requirements gathering process at the high level while I came up to speed. Now that I am settled in, I am creating the Use Case documents, updating the UC Diagram, and managing the project.
It has been an exciting introduction to the job. I'll keep everyone posted.
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Hi Micheal! Great work!
Just one thing that made me curious:
Originally posted by Michael D. Brown:
the target for getting a working initial build is March 10th (roughly 5 weeks after the project started).

Can you explain what you mean by "working"? Will you have a "running" system at the end of day 1 of construction?


The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Michael D. Brown
Greenhorn

Joined: Nov 22, 2003
Posts: 29
Originally posted by Ilja Preuss:
Hi Micheal! Great work!

Thanks a million, if it weren't for the feedback I received from everyone when I first joined the Ranch, I would be adrift at sea right now.

Can you explain what you mean by "working"? Will you have a "running" system at the end of day 1 of construction?

I WISH!! What I mean is I have planned our first iteration as a Structural Prototype. I'm going to provide the stakeholders (namely my boss, the CEO) with a walkthrough of the system that lets him do basic tasks. He'll be able to see how it looks and how things will work. That's what will be done March 10th (actually the coding is scheduled to be done March 2, but I'm giving our internal team a working week to test the system before we show it to the big boss).
The advantage of doing this is that it will give the team an opportunity to run through a relatively simple iteration and refine our process (and determine how good I am at estimating) before we go full stream...basically a trial run.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Progress on Process