File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Agile and Other Processes and the fly likes Numbers 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 "Numbers" Watch "Numbers" New topic


vasu maj
Ranch Hand

Joined: Jul 12, 2001
Posts: 396
How does a software developer become part of the numbers game? I agree it is important for a project to be launched with all the numbers done. But you mention the book is meant for developers. Can you explain why a developer needs to involve himself with these processes?

What a wonderful world!
Jane Cleland-Huang
Ranch Hand

Joined: Feb 28, 2004
Posts: 32
Vasu, this is a great question and probably the one that we have been asked the most since the launch of Software by Numbers. The answer is that we don't expect developers to be experts in this. What we do hope for is closer collaboration between software developers and business stakeholders (customers that understand marketing, financiers, business managers etc). It is these stakeholders who bring input on the value side of the equation.
IFM is only made posssible in presence of this type of collaborative effort. However the rewards can be significant.

Jane Cleland-Huang PhD<br />DePaul University<br /><br /><a href="" target="_blank" rel="nofollow"></a>
Ilja Preuss

Joined: Jul 11, 2001
Posts: 14112
As a developer, I very much depend on the financial decisions made by management. In my experience, it very much helps me working to those decisions when I understand how they are made.
Some months ago, typically our project managers just said "do this and that until next week". The problem with this approach was that you can put a wide range of effort into a feature - you can implement barely the minimum, or you can spend a great amount to make it easier to use, prettier, whatever. Of course what would often happen is that we were spending the effort at the "wrong" places.
Today, collaboration has improved - the whole team discusses how much value a feature has and why (not by using IFM but by a more ad hoc approach). This has greatly improved motivation, effeciency and perceived quality of the product.

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
Mark Denne

Joined: Feb 19, 2004
Posts: 11
This is an excellent point. Understanding how the financial decisions are made helps us as developers and architects to have a wider understanding of the context in which we are operating. However, the advantage of IFM is that it empowers you to actually contribute to those decisions. If the financial analysis is performed with the developers and architects at the same table as the stakeholders and the marketeers, this not only serves to breakd the divide of understanding and vocabulary but also provides better and more informed decision making for all parties. The result is a more coherent team and generally a more successful project.

Author - Software By Numbers<br /><a href="" target="_blank" rel="nofollow"></a>
I agree. Here's the link:
subject: Numbers
jQuery in Action, 3rd edition