Pivotal Tracker for Mozat

666 views

Published on

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

No Downloads
Views
Total views
666
On SlideShare
0
From Embeds
0
Number of Embeds
14
Actions
Shares
0
Downloads
6
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Pivotal Tracker for Mozat

    1. 1. Diving into Agile. Managing Productswith Pivotal Tracker.
    2. 2. What is Pivotal Tracker?• Pivotal Labs SaaS product for agile project management and collaboration.• Teams break down requirements into concrete stories arranged in a shared & prioritized backlog.• Workflow is based on “Extreme Programming” agile software development.• Supports Scrum.
    3. 3. Who is Pivotal Labs?• Agile software development consulting firm with headquarters in San Francisco.• Offices in Manhattan and Boulder, Colarado. Previously in Singapore.• Proponents of Ruby on Rails, pair programming, TDD and BDD.• Clients include Twitter, Best Buy, EMI Music, Mavenlink, Zendesk.• Acquired by EMC Corp. in March 2012.
    4. 4. Why Pivotal Tracker?• Used by leading practitioners of Agile.• Used by Twitter, New Relic, Get Satisfaction, Groupon, Engine Yard, Threadless, Thoughtbot, Balsamiq Studios.• Personal experience from using it to manage product at Found and ViKi.• Everybody knows who’s working on what.• In sync with reality.• Great for accountability and QA.• Really easy-to-use single-page interface.
    5. 5. How Pivotal Tracker is generally used. Let’s watch a short video.
    6. 6. Mozat Workflow1.Requirements Gathering2.Story Breakdown 2.1.Design stories (wireframes, hi-fi screens, assets) 2.2.Engineering stories (client, server)3.Story Estimation (developer, designers)4.Prioritization5.Make stuff (design, code)6.QA acceptance for deployment
    7. 7. Mozat Workflow1.Requirements Gathering2.Story Breakdown 2.1.Design stories (wireframes, hi-fi screens, assets) 2.2.Engineering stories (client, server)3.Story Estimation (developer, designers)4.Prioritization5.Make stuff (design, code)6.QA acceptance for deployment
    8. 8. Mozat Workflow1.Requirements Gathering2.Story Breakdown 2.1.Design stories (wireframes, hi-fi screens, assets) 2.2.Engineering stories (client, server)3.Story Estimation (developer, designers)4.Prioritization5.Make stuff (design, code)6.QA acceptance for deployment
    9. 9. Mozat Workflow1.Requirements Gathering2.Story Breakdown 2.1.Design stories (wireframes, hi-fi screens, assets) 2.2.Engineering stories (client, server)3.Story Estimation (developer, designers)4.Prioritization5.Make stuff (design, code)6.QA acceptance for deployment
    10. 10. Demo
    11. 11. Things to Note• Each Release Marker denotes an Iteration/Sprint (Scrum terminology).• Iteration Planning happens at the beginning.• Story Acceptance (by QA) happens the middle.• Daily Standups in the morning are useful for voicing out problems/road blocks.
    12. 12. Next Steps• Upgrade existing Pivotal Tracker plan to support higher number of collaborators.• PM, designers, engineers, QA to be added to each project.• PMs to start writing stories for their respective products.• PMs, design, engineering to do story breakdown and estimation for their respective products.• PMs to do prioritization.
    13. 13. Slides bit.ly/ mozatpt Videobit.ly/ptvid

    ×