Blog – Page 2 – Ars Agilis

Agile Artifacts: The Product Vision Statement

Posted on 16/08/2012 by Michael Chik

The first and foremost step in any project is to create the product vision statement. The vision statement is like a lighthouse, shining a beacon that you can see from afar. It's here so you can be sure you are moving in the right direction, regardless of whether it's dark, stormy or even when the

Posted in Product Management

Agile Artifacts: Understanding the Product Backlog

Posted on 14/08/2012 by Michael Chik

The product backlog is an ordered list of all project requirements. Started at the beginning of a project, this single list of requirements is arguably the most important artifact in any agile project. Requirements in agile projects generally follow the user story format. The product owner is responsible for creating, maintaining and for ordering the

Posted in Product Management

Changes to the Certified Scrum Master exam process

Posted on 09/08/2012 by Michael Chik

The Certified Scrum Master (CSM) exam certification process is currently going through some change. Until now, everybody who attended a Certified Scrum Master course and took the exam passed. However, starting from the 1 September 2012 the Scrum Alliance is going to update the exam content, slightly increasing the difficulty, and introducing a pass/fail outcome.

Posted in Scrum

Agile Manifesto: Responding to Change

Posted on 01/08/2012 by Michael Chik

Traditional project management methodologies have always tried to control the amount of change within a project. Change management procedures, meticulously scripted legal contracts and rigorous budget policies are designed to fend change off as long as possible and keep change within a project to a bare minimum. This has often led to “successfully” completed projects

Posted in Agile Basics Change Management

Agile Manifesto: Customer Collaboration

Posted on 31/07/2012 by Michael Chik

Traditional project management methodologies do a very good job in keeping the customer away. In fact, customer involvement in what was deemed completely successful projects amounts to merely two instances: once at the beginning and again at the end of a project. In slightly less successful project environments you may also have customer involvement when

Posted in Agile Basics