Re: [scrumdevelopment] Re: Freeware/open source SCRUM tool
- I have used Scrum Works basic for some projects, it is great and easy to use.
Now I'm using spreadsheets. I'm not using boards and cards cause currently I don't have environment for that and I'm working with distributed teams. The spreadsheet is going well and it is an easy point of contact for the whole team.
The software must help your team. But the team must be able to run a sprint without the tool.
Try not to use a software tool to control your sprint if you are able to do that in the beginning.
Just to make sure that the team is aware about how to work with the mechanics.
On Sat, Mar 8, 2008 at 7:01 AM, Michael Yang <michael.cy.yang@...> wrote:Well,We use Spackle as our scrum tool.regards,-MichaelOn Thu, Mar 6, 2008 at 7:17 PM, Murali Yelamanchili <murali_yelamanchili@...> wrote:Hi,
We use ScrumWorks Basic for our Scrum tool, which is still free. I won't say that it is the only tool we use. We use a combination of ScrumWorks, JIRA and Excel.
As for whether to use tools or not here is my take on it -
Let us not forget the reality today. In , where I work, we don't often have the luxury of large office spaces with large meeting rooms. Sometimes we make do by just huddling at the Scrummaster's desk and finish the standup. It is next to impossible to get a physical taskboard, because the office space comes at a premium.
It is not ideal, but the best we can do under these conditions. Just to give you an idea, our floor are seats 70 engineers, and we have only 1 room that can accomodate 10 members at best at a time. And there are 11 teams doing Scrum, and if we all want a taskboard in there, and all try to dash into the room for a meeting.
As Manager and Scrummaster, I don't particularly like what I have to do here.
Similarly, post-it notes are rationed, and not in full supply as and when we want them.
We use a distributed tool (ScrumWorks) because our Product Owner works out of . It works most of the time, except for when the PO is off the grid - I mean when he is on the flight or is not able to connect to the Internet (on the beach or a coffee shop :-) )
When he is not connected, he finds it very difficult to record his ideas into the Product backlog, because he cannot access Scrumworks, and uses an Excel spreadsheet to record his ideas, and then syncs it with the backlog inside Scrumworks when he is back on the VPN again. This is a manual task, because Scrumworks is not really good with export/import of information. But we don't waste time trying to fix it, but get along with it, the best we can, and work around it.
Above all this, I am required to produce an executive summary for my bosses once a Sprint ends, and the Scrum tool makes it easy for me as it generates most of the information I require for the report.
Do I like it? No - not really, but I have to do it.
My point is that tools are useful to those who really need them. I think most of us are sane enough not to use a tool just because it is fashionable, or makes us feel good.
The reality is a bit different than we would like it to be - In my case this means - no physical taskboards, no post-it notes (sorry no supply), shortage of markers and certainly no meeting rooms. And a PO, who needs offline access, combined with upper management who want executive summaries of Sprints.
Using tools makes my life as a manager and scrummaster easier to certain extent, and helps me concentrate more on what I else can do for the team. So I would certainly advocate using them, but also would state, like others have done here, we be judicious in our use of these tools and not think that they offer a solution to all our problems.
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.