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.

An in-depth definition of the spiral development model.

This article shows you how take advantage of cloud technologies by adapting your existing development and operating procedures.

Introduction
When developing corporate-level business applications (Enterprise Scale) customers often requires implementing support for extensibility of the application object model not modifying the system source code. Use of extensible domain model allows for development of new functionality without additional effort and overheads:

1) the application will be used for a more lengthy period
2) the system workflow can be modified over time when changing external factors
3) “setting” the application to fit specifics of an enterprise where it has been deployed.
The most simple and cost effective way to achieve the required functionality would be implementing extensible business entities in an application with the support of custom fields.

Spiral development is a family of software development processes characterized by repeatedly iterating a set of elemental development processes and managing risk so it is actively being reduced. This paper characterizes spiral development by enumerating a few "invariant" properties that any such process must exhibit. For each, a set of "variants" is also presented, demonstrating a range of process definitions in the spiral development family. Each invariant excludes one or more "hazardous spiral look-alike" models, which are also outlined. This report also shows how the spiral model can be used for a more cost-effective incremental commitment of funds, via an analogy of the spiral model to stud poker. An important and relatively recent innovation to the spiral model has been the introduction of anchor point milestones. The latter part of the paper describes and discusses these.

Systems exist to generate value for their stakeholders. Unfortunately, this ideal is often met only to a limited degree. Current development methods, such as waterfall, spiral, and agile often provide incomplete and inadequate direction to stakeholders, architects, and developers. Two essential concepts—value models and architecture strategy—are missing from many development processes; however, these concepts can be integrated effectively using the waterfall, spiral, or agile methods.

This paper argues that a successful switch from one methodology to another requires a switch from one ontology to another. Large-scale adoption of a new methodology means "infecting" people with new ideas about what sorts of things there are in the (software development) world and how those things hang together. The paper ends with some suggestions to methodology creators about how to design methodologies that encourage the needed "gestalt switch".