Monday, 12 January 2009

Will Borland Survive yet Another Crisis?

Borland discreetly announces this week the resignation of both Tod Nielsen, CEO since 2005, going to VMware as COO, and Peter Morowski, SVP of research and development, leaving the company to pursue other opportunities. Borland will also reduce its workforce by approximately 130 employees, or approximately 15 percent of its regular full-time staff. For the fourth quarter of 2008, Borland is expecting to report total revenue in the range of $38.5 million to $40 million, down at least 10% from previous quarter. Considering that operating costs of revenues for the third quarter were around $45 million and that a lot of them are fixed costs, this will be another quarter with an important operating loss for Borland. The current CFO will act as CEO.

In the past year Borland has often blamed its IDE division to be the cause of this problems, slowing its ambition to be an ALM leader with huge financial losses. In May, Borland finally managed to sell the CodeGear unit to Embarcadero. The financial results of CodeGear are now difficult to estimate, as Embarcadero is a private company. What is left at Borland is a mixed set of products, resulting of some in-house innovation and external acquisitions (Togethersoft, Segue), grouped under the “Application Lifecycle Management” banner. None of the components of this set is considered as a top leader in its specific market and good integration between existing products is always difficult to realize. Trying to sell these type products is more difficult, because you have to reach a higher level in the enterprise than for individual developer products. It is also the type of project that most companies will postpone in a period of difficult economic conditions. Furthermore, this put Borland in competition with bigger fishes, like IBM that purchased rival Telelogic last year, and companies like MKS that have their roots in the ALM market.

It would be a bad thing if Borland fails just after having celebrated its 25th birthday, but if it was already struggling in times where the economy was good, we could fear that survival would be even more difficult in the hard times that are ahead of us. Researching for this post, I found that Borland had already cut 40% of its workforce in 1995 after the resignation of its founder Philippe Kahn, so maybe we should believe that it could be just “another deep crisis” in Borland history, a company briefly knew under the name of Inprise ;o)

Borland full press release

Tuesday, 6 January 2009

Winter 2008 Issue of Methods & Tools

Methods & Tools is a free e-newsletter for software developers, testers and project managers. Winter 2008 issue’s content:

* Fingers in the Air: a Gentle Introduction to Software Estimation

* Behavior Driven Database Design

* Optimizing the Contribution of Testing to Project Success

* Service Components and Compositions

45 pages of software development knowledge that you can download from http://www.methodsandtools.com/mt/download.php?winter08

Wednesday, 10 December 2008

My 10 Favorites Agile Project Management Articles

This is a (personal) list of articles dealing with agile project management that I like. I have chosen to include material that is longer than the usual (short) blog posting. I encourage readers to give more objectivity to this subjective set by submitting in the comments what they preferred ;o)

Agile, Multidisciplinary Teamwork by Gautam Ghosh

The Agile Customer’s Toolkit by Tom Poppendieck

Bridging Agile and Traditional Development Methods: A Project Management Perspective by Paul E. McMahon

Managing the Work in an Agile Project by Dan Rawsthorne

A Governance Model for Incremental, Concurrent, or Agile Projects by Alistair Cockburn

Measuring Integrated Progress on Agile Software Development Projects by Tamara Sulaiman & Hubert Smits

Visualizing Agile Projects using Kanban Boards by Kenji Hiranabe

The Pomodoro Technique (The Pomodoro) by Francesco Cirillo

Agile Fixed Price Projects part 1: “The Price Is Right” by Pascal Van Cauwenberghe
Agile Fixed Price Projects part 2: “Do you want agility with that?”

The Need for Agile Project Management by Mike Cohn and Ken Schwaber

Additional agile project management article resources

Agile Alliance Library
Scrum Alliance Library

Agile Journal
DZone Agile Zone
InfoQ Agile Section
Methods & Tools Articles Archive
Mountain Goat Articles
Software Development Articles, Agile Section

Wednesday, 5 November 2008

More than 1000 tools registered at SoftDevTools.com

SoftDevTools.com is a unique directory of software development tool where you can be informed on both commercial and open source solutions for your software development needs. It covers all software development activities: programming (java, .net, php, ruby, etc), testing, configuration management, databases, project management, etc. Tools can be classified using multiple criteria: licensing, running platforms and functionalities, etc. With 10′000 monthly visitors, SoftDevTools.com is proud to have registered its 1000 tool and looking forward to reaching the 2000 milestone.

If you are the editor of a commercial software development tool or contributing to an open source project, go to http://www.softdevtools.com/ to register your tool.

Wednesday, 29 October 2008

Unit Testing Still Widely Informal

A recent Methods & Tools poll examined how organizations perform unit testing. Is it an informal activity that is done before integration if there is some time left after programming or is it the key element of the development effort? The question was: How is unit testing performed at your location?

Proportion 2008 2006
Unit testing is not performed 17% 13%
Unit testing is informal 40% 46%
Unit tests cases are documented 9% 11%
Unit tests cases and their executions are documented 14% 16%
We use a Test Driven Development approach 20% 14%

Participants: 384 (2006:460)

Ending date: October 2008 (February 2006)

Despite the fact that the number of TDD adopters has grown nicely since the previous survey, you can notice that unit testing is still widely conducted in a informal manner, when it is not simply ignored by developers. This could sound weird when many people announced a general adoption of the agile approaches, but the results of our survey are similar to many other polls on the same topic.

Comparing the two surveys, it seems that people that were already doing unit testing formally have switched towards a TDD approach. People that don’t do unit testing have different reasons. Some will consider simply that they don’t add value to their development process, which is sometimes difficult to believe. For others, it is the lack of time, a reason more easier to understand ;o) Many complains that unit test are hard to write, but creating a good unit test is a proof that you understand what your code should do. I agree however, that it could be difficult to maintain large libraries of unit testing scripts if requirements are changing constantly. In the “good” reasons not to perform unit testing, some thinks for instance that the client side of Web application is not suited for this kind of tests. There are also some organizations that have separate testing teams. Their developers will rely entirely on the QA guys to test their application. You can also consider that when the software has a very limited life expectancy, it is not worth making unit tests.