The Latest

This application tool allows non-programmers to produce working prototypes of Windows, or Web-based, database-driven applications. Read on to find out how this new tool makes protoyping a viable part of the IT software development process.

While most bugs that make headline news are due to careless software implementations exploited by skilled hackers, the problems in KaZaA center around its user interface. This article details KaZaA's application flaws and then suggests ways to prevent such flaws.

Chances are you won't be able to deliver on everything your customer wants. Asking good questions at the beginning of a project can help you determine where your customer wants to go. Although you may not be able to give them everything they want, if you are able to deliver the top ten things on a list of fifty items you've still delivered value. Keeping the lines of communication open is essential to helping you achieve your project goal.

Metrics are only worthwhile if you review and use them. Do your quality reports go directly from the inbox to the trash can? A quality metrics program can be a great asset to your organization. Engineering, sales, and the company overall can benefit from having such a program. This article will help you explore ways to make measurements meaningful outside of QA.

Starting a project without considering the risks is quite a gamble. Learn how to increase your odds through the practice of good risk management. Effective organizations recognize that bad stuff may happen during a project. Risk management is about anticipating what might happen, examining and prioritizing those possible bad events, and figuring out what to do about them. In this article, review the Risk Management Glossary and discover remedies to risks that may help you prevent many common problems.

This paper discusses how software projects following different processes, which display disparate characteristics, have been categorized and analyzed using statistical techniques to measure and improve process capability. The analysis shows that language type, size of the application and complexity (represented by ratio of Total Project Effort to Build Phase Effort) are the predominant discriminating factors affecting quality and process parameters. Categorization done based on this stratification scheme results in minimum variation within the group concerned. Such logical grouping also facilitates meaningful comparison of a project performance with almost similar historical data.

What all virtual teams have in common is that they are working on a project, but may not be located in close physical proximity, and they must find ways to communicate, track progress, and manage tasks without being able to physically meet regularly. The prerequisites for success with virtual teams are 1) clear, manageable objectives; 2) management's commitment to necessary resources; and 3) mature management and technical personnel. Learn how to lead a workgroup you cannot see.