We are a small, intelligent App development studio. We love "Building Amazing Apps", solving problems and cultivating strong relationships with our clients.
Recent Articles
- Deploying django using docker
- Common testing scenarios for Django app.
- Logging in Django
- Serving static files in Django
- Two Scoops of Django: Review
- Introduction to Python Workshop on February 15th, 2013
- Easy client side form validations for Django: Django Parsley
- MoreApps - Android Library Project: Open Sourced
- Tutorial: Building a Chrome app
- Password Generator App: Open Sourced
About Agiliq
Topics
Archives
- June 2013
- April 2013
- March 2013
- February 2013
- January 2013
- November 2012
- October 2012
- September 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- October 2011
- September 2011
- July 2011
- June 2011
- April 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- June 2010
- April 2010
- March 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- April 2009
- March 2009
- February 2009
- November 2008
- October 2008
- June 2008
- May 2008
- April 2008
The Unfuddle Tutorial
By : Shabda Raaj
Unfuddle is the tool we use for our non open source development. I have found it to be the best tool for Software Project management, in particular I think it is superior to Basecamp and Assembla.
When you start using Unfuddle, the number of things can seem overwhelming. This tutorial should help you Unfuddle the Unfuddle.
The Unfuddle Glossary
Unfuddle has,
Userworks on.tickets which should be completed before this given time.users.The tips
Work from a list.
All action item items should be a ticket for somebody. Everything which a
userneeds to work should be in his work queue.Make it easy to see everyone's work items.
When we start a project we create project reports with every
userticket queue.Manage cognitive overload
People should have less than 10 tickets in their queue. More than this leads to a paradox of choice, with making it hard to decide to work on. 5 is a good number of open tickets per person, with proving choices on what to work on next, without being overwhelming.
Prefer Unfuddle messages to email.
Unfuddle message threads are easier to refer to in conversation in tickets and other places, having a meaningful url.
Commit all your code.
All code should be in a central repo, which can be refered to from tickets and messages.
Commit messages should be meaningful.
This is a good commit message.
This will automatically attach this commit to the given tickets, making it easier to track why a change was introduced, and how did a bug get fixed.
Get all stakeholders on board.
Your project probably has many people who are acuustomed to keeping things on email. For them using a tool like Unfuddle would be a big change. You need to get them on board to use Unfuddle.
This was first in a series of tutorials we would be publishing for using Unfuddle. Stay tuned.
Related Posts
Can we help you build amazing apps? Contact us today.