Identifying risks associated with software development is vital for project success. In most cases, developers are aware of risks throughout development but potential problems are not communicated in a way that reflects uncertainty in project health.
Taxonomy-based risk identification is a loosely structured method for quantifying risks during the planning phase(s) of software development.
Among the extravagant web-based project management solutions on the web (Basecamp, @task, Wrike, VeoProject, Clarizen, FogBugz, …more) lies an overlooked gem called “Wiki.” A Wiki is a website designed for collaboration. Wikis allow multiple authors to create, remove, and modify content. The inherent collaborative nature of Wikis makes it a perfect addition to the project manager’s arsenal. Wikis cannot replace software written specifically for PPM, but Wikis can assist organizations during development. This article reviews the following:
Every Friday, developers and managers should meet briefly to discuss the successes of the previous week. A Friday Wrapup Meeting should include all team members regardless of their status, position, or present work-load. The meeting’s mood should be kept upbeat and the discussion should be used to highlight company successes and developer contributions over the past week. This article contains recommendations for conducting these meetings.