Scrum and other agile methods recognize that responsiveness to change is an important aspect of delivering projects. They also recognize that software development is evolutionary and creative. By managing changes through Adaptive planning, Scrum provides a simple yet effective method of planning and tracking project progress. In this article, we will examine what is needed to sustain Adaptive planning and improve Team's responsiveness towards customer needs.

We will examine the following factors:

•Just-enough planning
•Evolving plan, scope driven by budget and/or time

Scrum Methodology, I am sure you have heard of it. It seems like everyone is very excited about this Methodology. It seems to fit in well to control chaos in your Enterprise. It shifts responsibility from an individual Project Manager to the entire Team. The Team becomes responsible for the success and failure of the Project. Its a collaborative effort, no one is over anyone, everyone is equally responsible. It seems to be pretty successful, at least for us it is.

Here is a Video on what the Scrum Methodology is, hope you find it useful. Enjoy and have a nice day.

Scrum is an agile approach to software development. Rather than a full process or methodology, it is a framework. So instead of providing complete, detailed descriptions of how everything is to be done on the project, much is left up to the team. This is done because the team will know best how to solve its problem.

By John Clifford, CSM, CSPO, CSP

Many teams moving to Scrum have questions about the Product Owner position. Is the Product Owner a member of the Scrum team? What role does the Product Owner play in the day-to-day life of a Scrum project? How do we map current functional roles to Scrum roles, specifically with regard to the Product Owner? Who should we select as our Product Owner?

As a ScrumMaster, I was asked this question many times. Sometimes I had enough time to explain, sometimes not. But every time it was challenging to provide a clear picture of what a ScrumMaster really does.

To help myself and other ScrumMasters, I have started to write down general activities, which characterize the role of the ScrumMaster (see below).

The priority of activities varies by company.

1.Keeps Scrum process running
2.Ensures a proper power balance between PO, Team, Management
3.Protects the Team
4.Moderates in the Team
5.Helps to organize (e.g., Meetings)