Agile

Previously, an entry was written on how to Install Capistrano 3, on Debian. Here is an alternate, quicker way, of installing Capistrano using RVM, on any flavour of Linux – authored by Omar Tamer. This tutorial requires curl, and root level privileges. First stage is to install the ruby version manager,

As part of my learning process about Agile Methodologies, I am adding a few notes about Agile in general and some of its methodologies in particular. Part of a series of posts, the first entry is about the Agile Manifesto and Principles. This and the following entries rely on the

According to Ken Schwaber, co-creator of Scrum: “You can’t predict or definitely plan what you will deliver, when you will deliver it, and what the quality and cost will be”.  Scrum is focused on delivering working software regularly, monitor features delivered and adjust plans according to the results. Unlike

Capistrano provides server automation; by running a set of predefined scripts on remote servers. Puppet is a tool providing configuration management, provisioning and reporting. Puppet Enterprise extends Puppet by adding application deployment. Below is a quick introduction to what Puppet is, how is used and links to tutorials.  An Agile

Both Scrum and XP rely on User Stories to describe features required for delivery at the end of a Sprint/Iteration; and provide a basis for Time Estimates and Acceptance Criteria. This entry covers what User Stories and Acceptance Criteria are, how to write, and use. What are User Stories?

“Always be doing the most important thing that you can be working on.” – Kent Beck. While Scrum puts more emphasis on project management, XP is more focused on programming. XP surfaced from the need for flexibility, speed and quality. None of the XP practices are wholly new, but it takes

At the end of each Sprint/Iteration, team members (developers, customers, managers) get together and analyse how to become more effective.  What is a Retrospective? Retrospections are the time when processes are inspected in order to be improved, successes shared, real numbers are collected to be used for future projects

Once User Stories and Acceptance Criteria are created, developers being estimating tasks. This is done in a “Planning Poker”. Each team member having a set of “cards”, consisting of numbers in the Fibonacci sequence, and assigning a number in this sequence to each task. Planning Poker The Planning Poker aims