General discussion

Locked

Staffing OO development

By jevans ·
I am currently managing a large Object Oriented software development effort. Unfortunately, I have only managed "waterfall" type development in the past. I am struggling with putting together staffing plans for this type of development.

We are beginning architecture now, but I want to make sure that once we get into construction, I have the right number of resources with the right skill set.

We will be using WebSphere Application Server for our development environment using J2EE. Forthe analysis we will be using UML and the Rational tool suite.

Any ideas or reference material suggestions?

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Staffing OO development

by JoOehrlein In reply to Staffing OO development

I think you're confusing the design & programming methodology with the work break down structure. It's true that object oriented projects aren't usually done in a waterfall-style work flow, but they could be.

That said, I think that the information on Extreme Programming (http://www.extremeprogramming.org) offers a good explanation of iterative development. While some of their ideas might be considered, well, extreme, take what you want and adapt the rest. It'll give you an idea of the possibilities.

One used was to maintain a list of features broken down into priority groups -- do these first, these second, these third, etc. We allocated time for the first group and planned them at a detailed level (time for each step), while leaving the second group just with a chunk of time. As we neared the end of one group, we did detail planning for the next. I juggled the remaining features, as well as any bugs at the end of each cycle. In fact, I put all features in the defect tracking system and tracked everything -- features & bugs together as generic change requests. I liked it because it kept the project plan at a reasonable level of complexity. Developers liked it because they knew what to do next and felt like I paid attentionto their time estimates. They also didn't have to do a bunch of time estimates at the very beginning before they knew what they were getting in to.

As far as having enough resources and skill sets, just as in waterfall, it all depends on how goodthe time estimates are and how many unexpected things creep in.

One thing I would try to do is make sure that everyone is not new to this type of process methodology -- it's a lot more painful for everyone to be newbies.

Collapse -

Staffing OO development

by jevans In reply to Staffing OO development

Poster rated this answer

Collapse -

Staffing OO development

by Wayne M. In reply to Staffing OO development

In practice most OO software development is still done using a waterfall approach. I think you have already flagged the skill set you want to look for: Java and UML under Rational Rose. In terms of scheduling and man loading, I would use the same approach you have used in the past. If, however, you will be requiring new skills from your development team (i.e., this is their first attempt at either UML or Java), add in sufficient learning curve and schedule at least two releases, a prototype release and a final release. The last item is usually critical in developing with new technologies; you are going to have to go back and fix things in a second pass, so plan for it.

I hope this is the type of information you are looking for.

Collapse -

Staffing OO development

by jevans In reply to Staffing OO development

Poster rated this answer

Collapse -

Staffing OO development

by RealGem In reply to Staffing OO development

Well, I'm going to make this unanimous (so far). You can structure the development any way you like, once you know what it is that you are going to develop.

If you want to use the waterfall approach, go ahead.

However, I recommend that you use an incremental-build approach to drive shorter development-test-install cycles.

Focus on key objects first, because they will be the key building blocks (or roadblocks) to further development.

Collapse -

Staffing OO development

by jevans In reply to Staffing OO development

Poster rated this answer

Collapse -

Staffing OO development

by jevans In reply to Staffing OO development

This question was closed by the author

Back to IT Employment Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums