Scrum Software Methodologies

The Scrum model of software development has gained popularity over the past two decades and is seen by many as the ideal model for projects that need to be completed quickly and efficiently.

Software developed using Scrum methodologies are usually developed in short iterations or 'sprints'. Each day, the development team should meet to discuss what has been achieved, what steps are to be taken next and identify any problems that have arisen since the last meeting.

Also, each sprint should be planned in advance at a project team meeting, as should each completed sprint be reviewed by the team after completion. Ideally, the project team should be located in one place so it can self-organize and hold face to face meetings whenever necessary. A Scrum project does not have a project leader, as it is organized by the team as a whole, but it should have a 'ScrumMaster' who ensures that the team stays focused and makes sure that nothing distracts the team from the project goals.

The Scrum model of software development is all about flexibility. The customer is encouraged to get involved in the development process and it is accepted that the customer may ask for changes at any time. In a Scrum project there is an acceptance that requirements may change at any time and there is a willingness to adapt and change as necessary.

Backlogs

In Scrum projects the customer provides a list of requirements to the development team known as a product backlog. The team translates this into a sprint backlog which is a concrete set of tasks that need to be completed to meet the customer's requirements. The sprint backlog will contain actual information on how the finished product is going to be achieved.

Once the backlogs are prepared, the customer and the team meets to decide on how to proceed. This usually involves agreeing on what will be achieved in the next sprint. If any changes need to be made to the direction of the project they are usually made between sprints.

Pigs and Chickens

Anyone involved in a project using Scrum methodologies falls into one of two broad roles - pig and chicken. To simplify, those in the 'pig role' have a direct say in the project and the end product. These will include the customer, the project team and the ScrumMaster.

Those in 'chicken roles' are not directly involved in the project but can have an indirect influence in how it proceeds. These might include consultants, users and stakeholders.

 

Written by: Frank J Klein - CIO

Back to Articles | Next Article | Relativity | Watch the Video

Sign Up for Our Newsletter

Do you want more? Do you want to be notified of new blog postings and other exciting developments weekly? Do you want the competitive edge over your marketplace?

Sign Up for Our Newsletter and get Free Gifts when you Sign Up and Confirm Your Subscription:

Name:
Email:

• Monthly Updates and Informative Articles and Videos from our team of experts.
• White Papers and Free Training Offers
• Special Discounts and Incentives on our Services and Products
• Special Discounts and Incentives from our Channel Partners
• Monthly Prizes and Incentives for Blog Postings
• Much, Much More

Have questions or suggestions?

Contact Us By Email:

Email :
Company:
Name:
Phone :
Site URL:
Question or Request:
	I have read and agree to the terms of service