Are you using SCRUM?
My buddy Dallon Christensen and I have been using a workflow management system called SCRUM for project management and planning. So far we're loving how it works and I'm wondering if anyone else around here are using it for individual project management, group project management or distributed project management (like we're doing). If so, how do you like it? What tools are you using? And how have you arranged your system?
Nate
Replies to This Discussion
-
Permalink Reply by Kevin Lageer on -
Hey Nathan, That type of thing may be just what I am looking for...more on the individual project management side. Is it a paid or free program...do you have a link? Thanks for the help.
-
Permalink Reply by Dallon Christensen on -
Hi, Kevin,
I work as Nate's operations manager as a contractor for my own business. We were experimenting with different project management methods and really like scrum. I'm using it for my own projects, but I am making this a core offering of my business as I coach and work with small business owners. Allowing professionals to focus on becoming more profitable and doing what they do best is what I love doing.
The book Nate and I read as an introduction to scrum is called "The Elements of Scrum" (affiliate link to the Kindle version, but I also have a link to the hardback book on my site), and it's a good primer. I've developed a simple, spreadsheet-based program in Google Docs to track the progress on various sprints.
I love project management, but I hate the traditional and cumbersome manner project management is done. Scrum is a great way to really focus on a set number of tasks and make good progress quickly!
-
Permalink Reply by nathan miller on -
Kevin,
SCRUM is a concept/framework for getting projects to finished, not a paid program. I've tried way too many techniques but as a creative and a person with "shiny object syndrome" I couldn't keep to any one system for very long. SCRUM seems to be sticking a lot better than anything else (so far), however, I now have Dallon who I've hired to sort of keep my feet to the fire and help me stay focused.
I think his work has been key to me getting things done (ironically, Getting Things Done - "GTD" is another system I've tried), but it's been a long road. We've tried a bunch of different things - SCRUM seems to be our answer (so far). As we get rolling with the technique more and more I'm hoping to take on more work and be able to handle more projects simultaneously.
Hope this helps. :)
-
Permalink Reply by Seth Haigh on -
I like SCRUM.
I use an iPad App named iScrumboard. It is simple and helpful (not mine and I don't get money for recommending it).
I downloaded it to use because it helps to have a backlog of my "great ideas" that I can ignore until I'm ready to prioritize and pull a new lot from for action.
@sethhaigh
-
Permalink Reply by Seth Haigh on
-
P.S. iScrumboard is a free app.
-
Permalink Reply by nathan miller on
-
I use that app too. :)
I'd one of the highest rated iPad scrum apps around. Unfortunately I haven't been using it lately. Dallon and I have been playing with Podio and it's brand new iPad app. Podio appears to be perfect for scrum! :)
-
Permalink Reply by Seth Haigh on
-
I found this video when I was teaching myself about SCRUM. Not sure who made it. Still, I really like the content. It made learning the Agile SCRUM process simple and understandable.
-
Permalink Reply by Sergio T. Ruiz on -
i could go on and on.. but using scrum in a software development team, here are the things to think about:
- scrum works best when there is work being done on the project by more than one developer per day. this means that if there are three people hacking away at a project on any given day, you will get much more meaningful data.
- all team members MUST be on board with scrum. if you have people who balk at the idea of working this way, there will be confilcts, and scrum will most definitely get in the way.
- the software you use MUST be easy. you will most likely be logging your time with some other system also. that system is most likely an old and clunky system. if you have team members logging their time twice, the system you propose must be easy and get out of the way quickly.
- however you slice it, you must get management on board. tracking projects this way is indirect labor. if management sees to much of this, there could be trouble.
anyway, like i said, i could go on and on.. but let me know if you have any questions..
Search
Have a question or want to connect? Enter in some keywords here to see what we're already saying!
Weekly Podcast
Good stuff from 48days
© 2013 Created by Jon Dale.
