TDD in Ruby on Rails made easy

What is TDD? TDD, or Test Driven Development, is a software development process composed of three phases. These three phases work in incremental cycles until the functionality is ready. How does TDD work? Let’s describe how the TDD cycle would work to code a complex functionality. You would start the cycle by first adding a […]

Test Driven Development

Test Driven Development is a software development approach developed by Kent Beck. I personally find this technique very useful to deliver a good quality in your software, which must be always the goal for a good engineer, or also if you have signed a concrete test coverage with the client in the project contract. It […]

The Lean Startup: Create successful new businesses using Agile techniques

Last month I read the book The Lean Startup, by Eric Ries. In this book, the author tell us how to apply Agile techniques, such as the ones that we are used to in software development, to the creation of new Startups or to innovate on established companies. The author extracts the ideas from the […]

First impressions about Ruby

Since a few months I started to have interest on the Ruby programming language. As I am an agile enthusiast, I also wanted to give a try to a language that focus itself on coding and not on superfluous keywords or programming conventions, to a web framework (RoR, more of this on later posts) that […]

Sprint Backlog – Scrum Artifacts (and II) – Introduction to Scrum

Do you remember the “ready” or “actionable” items of the Product Backlog that we saw on wednesday? The Sprint Backlog is formed with the “ready” Product Backlog’s items that are selected for the Sprint by the Development Team in the Sprint Planning Meeting plus the plan to deliver an Increment and achieve the Sprint Goal. This […]

Product Backlog – Scrum Artifacts (I) – Introduction to Scrum

The Scrum Artifacts are documents that represent work or value to provide transparency and opportunities for inspection and adaptation. Today we will pay attention to the Product Backlog and the next day we will finish our Scrum’s introduction series with the Sprint Backlog. The Product Backlog is an ordered item list, in which each item […]

Scrum Events (and V) Sprint Retrospective – Introduction to Scrum

Today we will finish our overview to the Scrum Events with the Sprint Retrospective. This 3 hours proportional time-boxed event is focused on the Scrum Team’s improvement. The purpose is to inspect the Scrum Team itself and create an improvements plan for the next Sprint. How can we do it? First, we have to inspect […]

Scrum Events (IV) Sprint Review – Introduction to Scrum

The Sprint review is done at the end of the Sprint which the goal of inspecting the increment and adapt the Product Backlog. It is time-boxed to 4 proportional hours. It is an informal meeting to get feedback and increase collaboration, done between the Scrum Team and the Stakeholders, to review what was done in […]

Video: Agile Product Ownership

Today you will not find to much text. On friday I discovered this video of Henrik Kniberg in Javier Garzas’ blog. I wanted to share it with you because I think it supports perfectly the Scrum Introduction series I am writing at the moment. I hope you enjoy it. More about Henrik here.

Scrum Events (III) Daily Scrum – Introduction to Scrum

Today we are going to see the Daily Scrum. This is the only Scrum Event which duration is not proportional, that means that it is always time-boxed to 15 minutes independently of how long does the Sprint last. It is important to say that it must be always held at the same time to create […]