This article provides a basic overview of Scrum, an agile process for managing software development project.

This article is about applying Agile methods in an environ-ment that may be more familiar with high ceremony project manage-ment methods – methods that might be considered heavy weight in terms of today’s agile vocabulary.

In this article we are going to look at what many Project Managers and Project Management Professionals refer to as the "foundation" of the project, or at least the foundation of project planning. The Work Breakdown Structure (WBS). Creating a quality WBS will require a substantial amount of energy, time, and people, but in the end is not rocket science. Let’s take a look at the Purpose, Process, and Pitfalls of creating a Work Breakdown Structure.

While many brilliant books and articles have been written on good project management, there is little attention paid to all the possibilities a project manager has to create the appearance of managing a project well without the burden of actually doing it. The following article is a summary of such tactics, which I could not help noticing in many years of being involved in software projects. It is intended for project managers as well as people who monitor or supervise project managers, because we can prevent dirty tricks better if we have studied them.

Free software and open source projects are often perceived to be of high quality. It has been suggested that the high level of quality found in some free software projects is related to the open development model which promotes peer review. While the quality of some free software projects is comparable to if not better than that of closed source software, not all free software projects are successful and of high quality. Even mature and successful projects face quality problems, some of which are related to the unique characteristics of free software and open source as a distributed development model based primarily on volunteers.

People who have experienced good stand-ups will generally know what can be done when things aren't working well. This capability is obviously less likely for people with limited experience to reflect on. I've written this paper as an attempt to partly compensate for inexperience by describing the benefits and consequences of common practices for daily stand-ups. These patterns of stand-ups are intended to help direct the experimentation and adjustment of new practitioners as well as provide points of reflection to experienced practitioners.

This article presents techniques and tools used to create requirements with a team composed of the different participants of agile projects.

This article describes the Evolutionary Project Management. Evo is a project management process delivering evolutionary ‘high-value-first’ progress towards the desired goals.

An introduction to Business Value (BV), Earned Business Value (EBV) and Work Breakdown Structures (WBS) for Agile projects. The article demonstrates how BV can be calculated utilizing a WBS and how to calculate the other values for a given project.

This article defines the different process available for software development projects and when and how to use them.