The concept of planning within the agile methodology has often been misunderstood. Due to the commonly known statement “We value responding to change over following a plan” most of teams starting agile think that they will no longer need to plan for the future. Contrary to this popular opinion, planning plays just as big of a part in agile as it does in any other project management approach it is simply a little different.
Depending on where an organization is at in its systems development methodology journey, it may not be able to jump to a purist agile model and be successful. I’ve learned that the following six principles are paramount in a successful agile project.
In this article we are going to look at two of the most widely used agile methodologies, which are Extreme Programming (XP) and Scrum. Though they follow most of the same iterations, they differ in certain elements. Let us begin with Extreme Programming.
The first step in managing the risks to your project is to identify those risks. This article provides you with “how to” advice on identifying risks to software development projects.
The Sprint Review is conducted by any team member. People that may be present include the Scrum team and any other external customers, stakeholders or interested people that the Product Owner might invite. The Sprint Review generally consists of a demonstration of the work done, though not the sole or main purpose of the review.
By John L. Nelson Introduction Imagine an enterprise software development project where the customer says…