We manage the basic activities with simple todo lists from Jira. And we have quick, daily chats to see that folks are doing what they hoped to get done and have no blockers, and are coordinating as needed. This is via the Daily Scrum.
Typical daily steps:

• Always get the latest code from SVN repository
• Open up your jira page and select your next issue
• Start progress so folks know you are working on the issue
  • Conversely, if you have to put the issue down for a while, consider noting that you have stopped work on it.
  • If you can check in partial progress that doesn't break things, but will help other people keep moving with the latest code changes, then do so. However, this is mildly in conflict with our preference to check in clumps of related changes for a singular purpose. Do what's best.
    
• Write all necessary code, tests, etc. For example (assume you are starting from scratch and feature is from DB to GUI):
  • Create table by updating create.sql
  • Update insert.sql script with representative data (choose real data if you can find some)
  • Build code artifacts...
  • Build test artifacts see: Testing
  • Go all the way to implementing the services, etc.
    
  • Implement enough of a UI to prove your feature is working
  • Typically, complex UIs require a UI specialist and a bit more process to surface the final version
    
• You can prove things out with local build
  
• You can build on the DEV machine (or rely on the automated builds)