PHPMaster.com has posted a bit less of a technical article than usual and shares some of the concepts behind scrum, the project management style that's currently quite popular with development groups.

In an earlier article I wrote, we took a general look at project management and discussed what some of its pitfalls are that should be avoided. As part of that, I mentioned that you should, as much as possible, be using an Agile methodology, particularly Scrum, to manage development. I’d like to follow that up with a look at Scrum and at how we can use it to tame our projects.

He talks about the typical "waterfall" technique of project development - requirements up front and cross your fingers for the rest. He compares this to the agile process and how scrum, in particular, helps keep things from falling apart. He then gets in to "how to scrum" by defining some of the key terms and talking about things like:

• Holding smaller meetings
• Limiting scope and time frame
• Looking for feedback
• Constant reworking remaining time

...all at the same time, multiple times during the life of the project. Agile focuses on quick changes and updates because the project is constantly getting feedback from those asking for the product, giving them (hopefully) exactly what they want.

Referencing back to a previous post they made about the Scrum development method, the ThinkPHP blog has posted a HOWTO of sorts on getting this kind of development started.

In my previous blog post, I was asked how to implement Scrum in the first steps. My personal experience is that it's better not to directly begin with all the methods Scrum provides. Scrum requires changes in your internal business processes, so it's better to move ahead step by step instead of trying to get everything done until tomorrow (you see, incremental steps.

The main obstacles we experienced is in projects where you have moving targets - requirement changes every day. It requires a very good shape of discipline of all stakeholders in the project. See how we started...

He describes each step of the way, beginning with a meeting for the first sprint followed by a short sprint time - 5 days. They even mention a PHP app they've worked up to help track and manage this kind of development - a module for their PHProjekt software, the Scrum Addon.

Referencing back to a previous post they made about the Scrum development method, the ThinkPHP blog has posted a HOWTO of sorts on getting this kind of development started.

In my previous blog post, I was asked how to implement Scrum in the first steps. My personal experience is that it's better not to directly begin with all the methods Scrum provides. Scrum requires changes in your internal business processes, so it's better to move ahead step by step instead of trying to get everything done until tomorrow (you see, incremental steps.

The main obstacles we experienced is in projects where you have moving targets - requirement changes every day. It requires a very good shape of discipline of all stakeholders in the project. See how we started...

He describes each step of the way, beginning with a meeting for the first sprint followed by a short sprint time - 5 days. They even mention a PHP app they've worked up to help track and manage this kind of development - a module for their PHProjekt software, the Scrum Addon.

On the ThinkPHP blog today, bjoern has posted some of his opinions about Scrum, a programming methodology, and its use in the PHP world.

You may have heard about Agile Programming, eXtreme Programming and the like. I want to introduce to you Scrum, which is "an agile, lightweight process that can be used to manage and control software and product development using iterative, incremental practices.". Not only big companies are using this toolset, but also some smaller ones, including us at Mayflower GmbH.

He lists out some of the main attributes that Scrum is defined by, including:

• Scrum is a wrapper for existing engineering practices.
• Scrum is a process that controls the chaos of conflicting interests and needs.
• Scrum is a way to maximize productivity.
• Scrum is a way for everyone to feel good about their job, their contributions, and that they have done the very best they possibly could.

He's also given a workshop on the subject, and you can find the PDF slides here.

On the ThinkPHP blog today, bjoern has posted some of his opinions about Scrum, a programming methodology, and its use in the PHP world.

You may have heard about Agile Programming, eXtreme Programming and the like. I want to introduce to you Scrum, which is "an agile, lightweight process that can be used to manage and control software and product development using iterative, incremental practices.". Not only big companies are using this toolset, but also some smaller ones, including us at Mayflower GmbH.

He lists out some of the main attributes that Scrum is defined by, including:

• Scrum is a wrapper for existing engineering practices.
• Scrum is a process that controls the chaos of conflicting interests and needs.
• Scrum is a way to maximize productivity.
• Scrum is a way for everyone to feel good about their job, their contributions, and that they have done the very best they possibly could.

He's also given a workshop on the subject, and you can find the PDF slides here.