Tool Talk: Trello

1,787 views

Published on

Anuj Adhiya PLANITWIDE

Anuj Adhiya will show how PlanitWide, a 3-person startup, uses Trello-rather than email–for tracking task management internally.

Published in: Business, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,787
On SlideShare
0
From Embeds
0
Number of Embeds
880
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Just like things disappear in the Bermuda triangle ,email is where efficiency goes to disappear because it keeps getting used for things its not optimal for.
    All the things email gets used for…which it shouldn’t…
    Show of hands – how many in audience guilty of this?
  • When you're trying to manage who’s doing what, and when people don’t respond to emails, respond to incorrect emails, don’t use correct subject lines etc: Email thy name be hell
    But this is where a tool like Trello could come in and provide clarity to this mess
  • When you're trying to manage who’s doing what, and when people don’t respond to emails, respond to incorrect emails, don’t use correct subject lines etc: Email thy name be hell
    But this is where a tool like Trello could come in and provide clarity to this mess
  • When you're trying to manage who’s doing what, and when people don’t respond to emails, respond to incorrect emails, don’t use correct subject lines etc: Email thy name be hell
    But this is where a tool like Trello could come in and provide clarity to this mess
  • Its quite literally: “A whole new world”
  • ..and speaking of the world, let me briefly explain where the members of our team are:
    Anuj: BOS
    Porus: BOM or NYC
    KUNAL: another part of BOM
    External Developers: yet another part of BOM/India
  • Before getting into what trello is and how we use it, just a brief snapshot of what trello looks like.
    This is a trello board and as you can see its organized into lists
    Layout makes it highly flexible for managing anything that’s a to do or a process.
    As a completely non-technical team we’re using it in ways that perhaps aren’t expected of us.
  • And that’s what trello literally is…
    List of lists that’s
    web based and
    whose content is available in real time &
    asynchronously
  • Run through of card features
  • Card features 2: – What you can do with cards
  • We use it in 3 ways – represented by 3 boards
    - Some Connections between the ongoing tasks and other 2 – provided integrated/centralized workflow
  • Each member of team has their own lists for:
    To Do
    Doing
    Done
    Labels to identify types of tasks.
    If one person taking on too much of one kind of task, easy to see & balance workload
  • Each member of team has their own lists for:
    To Do
    Doing
    Done
    Labels to identify types of tasks.
    If one person taking on too much of one kind of task, easy to see & balance workload
  • Each member of team has their own lists for:
    To Do
    Doing
    Done
    Labels to identify types of tasks.
    If one person taking on too much of one kind of task, easy to see & balance workload
  • Each member of team has their own lists for:
    To Do
    Doing
    Done
    Labels to identify types of tasks.
    If one person taking on too much of one kind of task, easy to see & balance workload
  • Development process – how we build the sausage
    Took ideas from Trello’s & UserVoice’s development teams & added a couple of our own ideas to the mix
    Cards flow from: Master list>Next Up>In progress>QA>Launchpad>Live (each week that features went live in, has its own column)
    Each week having own Live column will help with controlling variables & maximize learning before adding more into the mix
    Labels:
    In Progress: labels to identify difficulty & progress within this step
    QA: label to identify bugs/tweaks
    Live: Deployed label
  • Development process – how we build the sausage
    Took ideas from Trello’s & UserVoice’s development teams & added a couple of our own ideas to the mix
    Cards flow from: Master list>Next Up>In progress>QA>Launchpad>Live (each week that features went live in, has its own column)
    Each week having own Live column will help with controlling variables & maximize learning before adding more into the mix
    Labels:
    In Progress: labels to identify difficulty & progress within this step
    QA: label to identify bugs/tweaks
    Live: Deployed label
  • Development process – how we build the sausage
    Took ideas from Trello’s & UserVoice’s development teams & added a couple of our own ideas to the mix
    Cards flow from: Master list>Next Up>In progress>QA>Launchpad>Live (each week that features went live in, has its own column)
    Each week having own Live column will help with controlling variables & maximize learning before adding more into the mix
    Labels:
    In Progress: labels to identify difficulty & progress within this step
    QA: label to identify bugs/tweaks
    Live: Deployed label
  • Development process – how we build the sausage
    Took ideas from Trello’s & UserVoice’s development teams & added a couple of our own ideas to the mix
    Cards flow from: Master list>Next Up>In progress>QA>Launchpad>Live (each week that features went live in, has its own column)
    Each week having own Live column will help with controlling variables & maximize learning before adding more into the mix
    Labels:
    In Progress: labels to identify difficulty & progress within this step
    QA: label to identify bugs/tweaks
    Live: Deployed label
  • Development process – how we build the sausage
    Took ideas from Trello’s & UserVoice’s development teams & added a couple of our own ideas to the mix
    Cards flow from: Master list>Next Up>In progress>QA>Launchpad>Live (each week that features went live in, has its own column)
    Each week having own Live column will help with controlling variables & maximize learning before adding more into the mix
    Labels:
    In Progress: labels to identify difficulty & progress within this step
    QA: label to identify bugs/tweaks
    Live: Deployed label
  • Development process – how we build the sausage
    Took ideas from Trello’s & UserVoice’s development teams & added a couple of our own ideas to the mix
    Cards flow from: Master list>Next Up>In progress>QA>Launchpad>Live (each week that features went live in, has its own column)
    Each week having own Live column will help with controlling variables & maximize learning before adding more into the mix
    Labels:
    In Progress: labels to identify difficulty & progress within this step
    QA: label to identify bugs/tweaks
    Live: Deployed label
  • Development process – how we build the sausage
    Took ideas from Trello’s & UserVoice’s development teams & added a couple of our own ideas to the mix
    Cards flow from: Master list>Next Up>In progress>QA>Launchpad>Live (each week that features went live in, has its own column)
    Each week having own Live column will help with controlling variables & maximize learning before adding more into the mix
    Labels:
    In Progress: labels to identify difficulty & progress within this step
    QA: label to identify bugs/tweaks
    Live: Deployed label
  • Development process – how we build the sausage
    Took ideas from Trello’s & UserVoice’s development teams & added a couple of our own ideas to the mix
    Cards flow from: Master list>Next Up>In progress>QA>Launchpad>Live (each week that features went live in, has its own column)
    Each week having own Live column will help with controlling variables & maximize learning before adding more into the mix
    Labels:
    In Progress: labels to identify difficulty & progress within this step
    QA: label to identify bugs/tweaks
    Live: Deployed label
  • Development process – how we build the sausage
    Took ideas from Trello’s & UserVoice’s development teams & added a couple of our own ideas to the mix
    Cards flow from: Master list>Next Up>In progress>QA>Launchpad>Live (each week that features went live in, has its own column)
    Each week having own Live column will help with controlling variables & maximize learning before adding more into the mix
    Labels:
    In Progress: labels to identify difficulty & progress within this step
    QA: label to identify bugs/tweaks
    Live: Deployed label
  • Certain tasks require referencing 3rd party resources (eg how to set up wordpress or tips for email ists, how to set up GA reports, business metrics monitoring etc.
    Created a KB of those resources for easy reference
    The kinds of things in our KB
    Each list – main topic
    Cards within a list – sub topics
    Comments within cards host urls
    Links KB cards that will aid with any ongoing task cards where appropriate.
    Also used as training tool.
  • Trello = The Force
    Completely expanded our horizons as to how efficient we really could be – can see/do things that just weren't possible before.
    We feel like Luke Skywalker.
  • If you go to www.planitwide.com/oo:
    Links to templates of our boards for you to copy
    Knowledgebase is exact copy with all resources we’ve found as of today.
    Questions? Tweet me @AnujAdhiya
  • Tool Talk: Trello

    1. 1. CLARITY TR
    2. 2. File Storage Team Collaboration 1:1 Team Communication External Communication Customer Communication
    3. 3. EMAIL
    4. 4. EMAIL
    5. 5. TR CLARITY
    6. 6. TEAM DISTRIBUTION
    7. 7.  List-of lists  Web based  Real-time  Asynchronous
    8. 8. KNOWLEDGEBASE DEVELOPMENT ONGOING TASKS
    9. 9. ONGOING TASKS Anuj: To DoAnuj: To Do Porus: To Do Porus: To Do Kunal: ToKunal: To
    10. 10. ONGOING TASKS Anuj: To DoAnuj: To Do Porus: To Do Porus: To Do Kunal: ToKunal: To Anuj: DoingAnuj: Doing Porus: DoingPorus: Doing Kunal:DoKunal:Do
    11. 11. ONGOING TASKS Anuj: To DoAnuj: To Do Porus: To Do Porus: To Do Kunal: ToKunal: To Anuj: DoingAnuj: Doing Porus: DoingPorus: Doing Kunal:DoKunal:Do Anuj: DoneAnuj: Done Porus: DonePorus: Done Kunal:Kunal:
    12. 12. ONGOING TASKS Anuj: To DoAnuj: To Do Porus: To Do Porus: To Do Kunal: ToKunal: To Anuj: DoingAnuj: Doing Porus: DoingPorus: Doing Kunal:DoKunal:Do Anuj: DoneAnuj: Done Porus: DonePorus: Done Kunal:Kunal:
    13. 13. DEVELOPMENT Master ListMaster List
    14. 14. DEVELOPMENT Master ListMaster ListNext UpNext Up
    15. 15. DEVELOPMENT Master ListMaster ListNext UpNext UpIn ProgressIn Progress
    16. 16. DEVELOPMENT Master ListMaster ListNext UpNext UpIn ProgressIn ProgressQAQALaunch PadLaunch PadLive (Week #)Live (Week #)
    17. 17. DEVELOPMENT Master ListMaster ListNext UpNext UpIn ProgressIn ProgressQAQA
    18. 18. DEVELOPMENT Master ListMaster ListNext UpNext UpIn ProgressIn ProgressQAQALaunch PadLaunch PadLive (Week #)Live (Week #)
    19. 19. DEVELOPMENT Master ListMaster ListNext UpNext UpIn ProgressIn ProgressQAQALaunch PadLaunch Pad
    20. 20. DEVELOPMENT Master ListMaster ListNext UpNext UpIn ProgressIn ProgressQAQALaunch PadLaunch PadLive (Week #)Live (Week #)
    21. 21. DEVELOPMENT Master ListMaster ListNext UpNext UpIn ProgressIn ProgressQAQALaunch PadLaunch PadLive (Week #)Live (Week #)
    22. 22. For BlogFor Blog KNOWLEDGEBASE For Email MarketingFor Email Marketing Web AnalyticsWeb Analytics Business MetricsBusiness Metrics
    23. 23. “You’vetaken your first step into alarger world” - Ben (Obi-Wan) Kenobi Star WarsEpisodeIV: A New Hope
    24. 24. www. .com/oo @AnujAdhiya KNOWLEDGEBASE DEVELOPMENT ONGOING TASKS TEMPLATES

    ×