yesterday between such exit Windows 8, there was a series of tweets between @ lfraile, @ javierholguera, @ r_corral and signing the post (which perhaps not that writes), where discuíamos the subject follow or not follow those guides that they propose us certain work as e.g. SCRUM methodologies.
So where have understood the context, Javier is asking if SCRUM is the form of work that best fits his scenario work, that he understands that he has to finish an iteration to release the result of the implementation of the users stories that have been defined for the same. I guess that it is why is being a little try KANBAN to manage its work, since in this way. For example, in the following table we see that if the WIP team is 5, the tasks that are about to close are the D, E, G and H;and that the released features in A and B can already prove.
As well, that helps in KANBAN have a closed element when”closed” and not having to wait for end of an iteration to release it.
But why not change the scope of a Sprint? (vale have already spoken of iterations, change to SCRUM mode)… then because the great Ken Schwaber in his book “AGILE PROJECT MANAGEMENT WITH SCRUM”, in addition to closing within 30 days the fixed period for a SPRINT, reads as follows:
“No one can provide advise, instructions, commentary or direction to the Team during the sprint.” ”The Team is utterly self-managing.“
Reading this at the bottom of the letter and being very hard in the SCRUM implementation; if during a sprint I have in estimated close 3 elements, I have to wait until the end of the sprint to unlock these 3 elements.
But it is very common to arise the following questions:
- What happens if I work in a team that creates common elements for other teams, and the first element is crucial so that another computer can continue working?
- should I do if my computer is able to deliver this item within 15 days, but the sprint is closed in 30 days?
- KenS proposes 30 days sprints, I change the size of a sprint?
Okay, we get to the interesting point:
I jump I rules/obligations that brings each methodology?
Because there is no correct answer for this. From my experience I always recommend a way of working with the same in-depth knowledge, learn to use what you really need.
An example, a while ago I participated in a project with a partner where we advise by SCRUM recommendations (based onTFS2010 and MSF for AGILE 5.0). But… not used to do daily scrum meetings! !!! If if if I already know it, the gurus of SCRUM creaking me. I am a sacrilegious, I’m not worthy, etc. If for KS, both should be close to €100 to the piggy bank, should always have the meeting in the same place, etc.; Let KS us kills.
But my question was, what we will do a Daily Scrum Meeting if both sitting side by side, we share 15 minutes from cafe where we talk about football, gadgets and the project;? do and also compatirmos hours of beers where also hablamso of the same?. Let that not need us.
When I think a bit, I see that this is part of my way of being. As I am a person who live on the edge, in the earlier draft which I shared with the partner nor did “stand-up meetings” (now changed to AGILE), after working briefly with a person you know and that can help quite a teamwork dynamics.
Clarification: This does not mean that the practice of the SUM is highly recommended, moreover there is an article on the site of Martin Fowler describing some recommendations to bring this type of meeting.
Personally, I think that without making the DSM not complicit work mode SCRUM. But we saltábamos the rules based on our experience and because we knew that this was the best way to work.
Now is time to ask, what I try to make everyone to ask:
Can I change the way in which I work to be more effective, without losing quality?
Because there you you have.
Greetings @ Home
PS: the Kanban chart is the new librako that I am just finishing, to see if I make a post/contest to see that title I put book.
PD2: I know that one after reading this will fail to read my blog… therefore more relief for the internet