Blog

Tag management on a virtual taskboard

 

Working with Scrum gives you the advantage of having at any moment a total overview of the status of your project: You have the burndown charts hanging around (product level, release level, sprint level), probably some function breakdown chart and most importantly, you have the taskboard that gives you the complete overview your sprint. 

 

scrum room

 

The taskboard gives you an overview of all stories the team committed to.

The Virtual Taskboard in Scrum - Basic funtionalities

 

The heart of Scrum is the taskboard. It’s a commonly accepted statement, and we do believe in it. That is also the reason why we took great care of this feature when we implemented it in our pmScrum product.

Our starting point was that the virtual taskboard should behave like a physical taskboard (with similar ease of use and flexibility) but on top of that, if offfers also the advantages of an automated, virtual system.

This is the general result:

 

10 Things to do in Sprint 0

 

Quite often Scrum projects and teams assume that they can start developing as from day 1 of the project.

This is only partially true and depends on your definition of ‘Start of the project’.

 

If ‘Start of the project’ for you is defined as “we have our team ready, give me the prioritized backlog, we’ll estimate so we can start developing”, then you can indeed start developing immediately.

However in most of the cases, you don’t have a backlog, a team... ready when the GO for a project is given. In these cases you need to do a ‘Sprint 0’.

Risk management - The Risk Rule of Three

 

Risk management is one of the more important aspects in project management.

As project manager your responsibility is to help your team to avoid and get rid of the issues and risks that lay all over the bumpy road towards project success.

On the other hand there is also a risk :-)  that you’ll spend much valuable time in analyzing and finding mitigations for things that might never occur.

 

So how should you tackle it then?

My (pragmatic and default) answer: use your common sense.

To avoid spending too much time on unsure, useless things but still be able to identify the most important risks for your project, I developed a simple guideline. I call it my Risk Rule of Three).

DoRR - Definition of Ready for Release

We are all familiar with the definition of ready and with the definition of done for stories on a scrum project. But as mentioned many times by many people the DoD of a story is often not enough to relase the 'Done' story to our customers.

That is why terms like DoD and concepts like 'Done, Done' were introduced. I would like to present you (yet) another one :-) : DoRR.

 

Fixing bugs during our scrum - How we do it

We are a scrum team developing a product that is never finished. We have had some problems with bugs in the past. Bugs kept reappearing, causing a lot of work at the end of the sprint to fix them all. To deal with this problem, we've come up with a few rules.

Agile Engineering - Continuously Monitoring the Sprint

TenForce Donuts

Our pmScrum software is developed using agile engineering. To make sure we don't let go on that one, we created our scrum monitor to continuously monitoring the status of our sprint.


Our pmScrum software is developed using agile engineering techniques. One of our references, to check if we are doing it correctly, is the JoelTest. We try to stick as close as possible to the Joel Test.
(http://www.joelonsoftware.com/articles/fog0000000043.html).

 

The Joel Test is basically a list of questions you can answer with a simple yes/no:

 

  • Do you use source control?
  • Can you make a build in one step?
  • Do you make daily builds?

How to convince your executive to use Scrum (part 2)

TenForce Donuts

How to convince your executive to use Scrum? That' the way I do it.

Compare the moment when you can start making money out of your project (and release it).

In my professional life I regularly have to convince executive stakeholders about the benefits of agile development or Scrum. In a previous article (http://www.scrumalliance.org/articles/326-how-to-convince-your-cfo-to-use-scrum) I explained one possible strategy, which we used for our internal management. In this article I would like to share another strategy you can use to convince management to do a project using Scrum.

Experimenting with OData as API

TenForce Donuts

Being agile, means being flexible. This does not reflect only to the team and co-workers but also to the technologies being used by our application.

 

Retrospective on “Challenges when introducing Scrum in corporate environments” talks

TenForce Donuts

Last month we did 2 talks on the challenges of introducing Scrum in corporate environments. 
One for a group of Scrum practitioners, already using Scrum
Another for the PMI Belgium chapter members, a diverse group of experienced project managers.