The best project managers know to superbly manage the subtleties of risks, employee turnover, personality clashes, shifting priorities, and other unexpected events. And they know how to motivate even mediocre employees to produce exceptional results. The biggest challenge is facing the fact that no project proceeds predictably and according to plan. Learn practical day-to-day techniques you can use to achieve extraordinary project success in spite of seemingly insurmountable setbacks.
The communication of functional requirements and specifications is the most difficult, critical, and error-prone task in IT projects. Research has shown that projects that proceed to the construction and coding phase with missing or wrong functional requirements and specifications are almost certain to fail. To avoid missing or misunderstanding the requirements for a solution, and to avoid the development of systems to incorrect specifications, we need a systematic approach to capturing, organizing, and validating the functional requirements and specifications. In this article, Bill Walton offers such an approach.
Most of us wouldn't think of launching on a critical journey without some forethought about destination, route, and risk. Why would software projects launch with anything less? In this column, Becky Winant explains how and why to create a project charter.
To get good requirements, you have to ask good questions. But what makes good questions, and how can you use them to systematically uncover requirements? In this column, Becky Winant shares the art and science behind asking questions that work.
Yogita works as a QA/testing professional with Mindfire Solutions, and has written a number of articles on QA and testing strategies. Yogita is currently exploring thoughts of beauty as an area of testing and its relation to usability. Her role at Mindfire has been to implement Quality processes throughout the organization and build a dedicated testing team. The team recently published a White Paper “Porting projects: Test techniques,” downloadable from www.mindfiresolutions.com. Yogita can be reached at [email protected].
Organizations face many problems that impede rapid development of software systems critical to their operations and growth. This paper discusses model-based
development and test automation methods that reduce the time and resources necessary to develop high quality systems. The focus is how organizations have implemented this approach of model-based verification to reduce requirements defects, manual test development effort, and development rework to achieve significant cost and schedule savings.
Errors in requirements specifications translate into poor designs, code that does the wrong thing, and unhappy customers. Requirements documentation should be inspected early and often. Anything you can do to prevent requirements errors from propagating downstream will save you time and money. Karl Wiegers shows you how.
Do you think the assumptions you make about your software project are important? I do. One of the biggest sources of software project failure is hidden assumptions, especially about your requirements. These assumptions have a way of coming out of the woodwork–usually at the worst possible moment–to foil your projects. But there are ways to track down and expose assumptions.