My two least favourite business terms
There are two business, project management terms that I have come to hate. They are used all the time where I work by the business, requirements team and anyone higher up the chain then I am. The two terms are: “risk management” and “traceability matrix”. I personally hate them because they are what I will call “waterfall words”. They are indicators that agile development is light years away from being adopted.
I dislike the first term–risk management–because it means that something somewhere wasn’t signed off. Yep, where I work, risk management is a bad thing because it means that the client has not signed off some part of the project prior to working on that part of the project. As I said, this is pure waterfall.
The second term–traceability matrix–is all about documentation. *Everything* needs to be documented. And not only documented, but cross referenced, indexed, and numbered. In fact, they just spent $2,000/user to buy a tool that will help them with traceability. This term also means that the developers cannot do anything unless that something can be fully justified via some document somewhere.
The end result of both of these terms is that developers end up sitting around a lot until everything is signed off and documented. This is not agile development. The funny thing is that someone showed me a document that clearly stated that to implement Agile with a big team, all you needed where the right tools. And of course, the article was trying to sell some overpriced tool from IBM that could handle testing, integration, and documentation.
Hey what IDE tool do you use for your java projects? There is a myriad of IDEs its mind boggling?
I tend to use NetBeans for most things that I work on, but I also like to use Eclipse. I have been really impressed with Eclipse 3.2 and the different plug-ins released as part of the Callisto project. For anything web related though, I use NetBeans. It just makes web stuff soooo easy.
Your open source project http://code.google.com/p/teamdocs/source doesn’t open up in NetBeans 5.5 why?
You have to set it up first as a NetBeans project. I have purposely not included any IDE project stuff (NetBeans, Eclipse, etc) in the Subversion repository. This allows people to use whatever IDE they wish.
I do know that the project will work in NetBeans 5.5 though since that is the IDE that I use to develop it. However, I may need to add a section to the project’s website that details how to set it up in NetBeans.
The general idea is to set it up as a web project with existing sources. NetBeans will then find the build.xml file and ask to substitute its own. Definitely accept this and allow NetBeans to manage the project. This will allow you to launch the project in the embedded Tomcat server.
Hi. It looks logical - but on the other hand - why workers need to work, and mostly to work hard, when the client has shown little symbol of his or her readiness for the process.
?