Shape Shift - XP 2009

516 views

Published on

Shape Shift is a JIRA plugin devoted to manage large distributed Agile Teams.

These slides were presented by Fabio Armani during the XP 2009 Conference

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

  • Be the first to like this

No Downloads
Views
Total views
516
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Shape Shift - XP 2009

  1. 1. Makes Jira AgileXP 2009 Conference© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  2. 2. Makes Jira Agile© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  3. 3. Who we are … Fabio Armani CTO @ Sequenza SpA - DEDAGROUP Agile Consultant & Traineer, Scrum Pratictioner Massimiliano Dessi Software Architect @ Pronetics SpA Author of: Spring 2.5 Aspect Oriented Programming© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  4. 4. Agenda Do We Need Another Tool? Background Challenge Why Jira? Make Jira Agile Integration In An Open Agile Suite Questions© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  5. 5. Agenda Do We Need Another Tool? Background Challenge Why Jira? Make Jira Agile Integration In An Open Agile Suite Questions© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  6. 6. Do We Need Another Tool?© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  7. 7. Why Do We Need aTool?•  Lets assume that we have a large and shiny nail. What is the best tool for the nail? Hopefully, the answer is obvious to most of us. Now, lets assume that we have a development team and a "shining“, promising, cool new agile development process. Most likely the hammer will not help.•  To tackle this problem, it is essential to have at your disposal a tool that enables requirements gathering, iteration planning, progress tracking and reporting. You cant rely on memory for requirements gathering. You cant rely on the universal perception for iteration planning and you definitely cant rely on telepathy for progress tracking and reporting. You need a tool that will do the job with minimum effort and minimum side effects.•  “I think that people and how they interact on a project are the most important thing, and I think that they need to create a way of working -- a process -- that works best for them. Because their interactions are critical to project success, I suggest that teams begin the work with an approach that will bring them together as people, not one that will let them remain apart, communicating electronically”. Ron Jeffries © 2008 Pro-netics S.p.A. The information contained herein is subject to change without notice
  8. 8. Agenda Do We Need Another Agile Tool? Background Challenge Why Jira? Make Jira Agile Integration In An Open Agile Suite Questions© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  9. 9. Agile Fractal Process© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  10. 10. Lifecycle - Scrum© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  11. 11. BackgroundIn the beginning Agile was …© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  12. 12. Background© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  13. 13. BackgroundNow we have a lot of Agile Tools …© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  14. 14. Background•  Currently there are different kind tools: •  Simple tools (whiteboards, cards on walls …) •  Tools which are specific to a methodology (ie: ScrumWorks, XPlanner) •  Methodology Agnostics Tools •  Application Lifecycle Mangement (ALM) that are complete but expensive tools (VersionOne, ResultSpace)© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  15. 15. Tool Categories•  The table below contains results of project management tools usage taken from TargetProcess leads (from May to July 2008). Most likely, many people in the "None" category use paper and whiteboards. However, it is just an assumption. [source; TargetProcess]© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  16. 16. Background•  24% companies use traditional project management tools (vast majority use MS Project)•  16% use Spread Sheets (vast majority use MS Excel)•  12% use various Bug Tracking tools (JIRA is the winner in this category)•  11% use Agile Project Management Tools (open source XPlanner is a leader) [source: TargetProcess] © 2008 Pro-netics S.p.A. The information contained herein is subject to change without notice
  17. 17. Agenda Do We Need Another Agile Tool? Background Challenge Why Jira? Make Jira Agile Integration In An Open Agile Suite Questions© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  18. 18. Challenge•  An Enterprise Agile Tool should support and satisfy a set of key features.•  An Agile Tools should aims at be a transparent and lightweight wallet to your process and day by day job of team members.•  Seamless integration of different tools (i.e.: IDE environment, Issue Tracker, Project Management Tool…).•  Agile Teams should be collocated but Open Source development demands for distributed “virtual” teams spread across the Globe. How can we manage it?© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  19. 19. Challenge•  1. Iterative, Feature-driven Development Although it may seem to be an obvious mismatch, many teams attempt to use a series of traditional tools that complicate their work because they dont support basic Agile practices.•  2. Integrated Lifecycle Management Tracking project information in multiple tools can inhibit accurate, real-time visibility.•  3. Cross-Functional Teams True support for cross-functional teams means consolidating and facilitating the project planning and tracking needs of customers, product management, project management, programmers, testers, etc. in a single environment for improved collaboration and consistency.•  4. Flexible Configuration A scalable management tool should allow organizations to define, organize, and plan according to their unique organizational requirements.•  5. Simplicity Like agile development, the more simple the tool the better. Most importantly, tools should never replace the benefits achieved by using the Agile practices - an Agile lifecycle management tool is only as good as the process it facilitates and the people that use it.•  6. Enterprise Scale An agile tool for deployment within an enterprise must be able to handle a sophisticated project structure and thousands of features and defects. © 2008 Pro-netics S.p.A. The information contained herein is subject to change without notice
  20. 20. Challenge•  Modern agile project management software combines common activities and provides open API for advanced integration.•  It powers: •  User Stories and Epics management. •  Backlogs prioritization. •  High level release planning and low level iteration planning. •  Progress tracking via virtual Burndown Charts, Task Board and Daily Progress. •  Tests management via Test Cases support and integration with automated testing tools. •  Bugs management via Bug Tracking support and integration with external bug tracking tools. •  Customers’ requests management via Help Desk functionality or integration with third-party tools like Salesforce.© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  21. 21. Agenda Do We Need Another Agile Tool? Background Challenge Why Jira? Make Jira Agile Integration In An Open Agile Suite Questions© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  22. 22. Why Jira?JIRA Solutions – Jira could be used to support different solutionsAnd it’s a standard de facto.© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  23. 23. Bug TrackingCustomisable, powerful defect tracking designed for teams large and small.JIRA is a system developed to track, manage and close bugs. More than 8,700 organisations depend on JIRA because it offers: straightforward tracking that follows the entire life of a bug integration within your IDE and other development systems flexible security strong reporting and project tracking capabilities© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  24. 24. Bug Tracking© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  25. 25. Project ManagementTrack, allocate and report on project tasks with real-time statistics.It can be a nightmare trying to keep track of all the tasks in a project. JIRA helps you manage and complete each task according to your workflow to ensure nothing slips through the cracks.© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  26. 26. Agile Software DevelopmentEstimate, allocate and track your iterations. •  Extreme Programming. •  Scrum. •  Lean Development. •  Feature-Driven Development. Agile development methodologies have revolutionised the way we develop software. It helps teams to deliver higher quality code more quickly, more frequently and in better alignment with what customers really want.© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  27. 27. Technical Support / HDEscalate cases, monitor response statistics and manage team workload.© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  28. 28. Opensource projects using Jira© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  29. 29. Highly Customizable The success of Jira is based on: •  Wide range of aviable plugins for al the needs •  sdk-plugin that allows to write custom plugins •  Fully customizable interface, dashbord and so on •  Fully customizable "skin"© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  30. 30. Jira and TasksA key point of Jira is the Creation of task and sub-task.<screenshoot here> © 2008 Pro-netics S.p.A. The information contained herein is subject to change without notice
  31. 31. Jira Dashboard© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  32. 32. Points iterations chart© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  33. 33. Gantt© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  34. 34. Stories© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  35. 35. Stories overiterations © 2008 Pro-netics S.p.A. The information contained herein is subject to change without notice
  36. 36. Jira with IntelliJ IDEA© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  37. 37. Jira with Eclipse© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  38. 38. Jira talks with IPhone© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  39. 39. Jira and Green Hopper© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  40. 40. AgendaDo We Need Another Agile Tool?BackgroundChallengeWhy Jira?Make Jira AgileIntegration In An Open Agile SuiteQuestions© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  41. 41. Make Jira Agile•  Don’t reinvent the wheel!•  Build the new tool as a plugin on the Jira platform allows us to take advantage of: •  Other Plugins Integration •  Open Solution© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  42. 42. ShapeShift•  Vision© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  43. 43. ShapeShift•  Main features: •  Planning management of release and iteration •  Independent definition of values and story points •  Automatism to aid in release planning and estimations •  Agile prioritization using MoSCoW (taken from DSDM) •  Must have (or Minimum Usable Subset) •  Should have •  Could have •  Wont have (but Would like in future)© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  44. 44. ShapeShift•  Must Haves are features that must be included before the product can be launched. It is good to have clarity on this before a project begins, as this is the minimum scope for the product to be useful.•  Should Haves are features that are not critical to launch, but are considered to be important and of a high value to the user.•  Could Haves are features that are nice to have and could potentially be included without incurring too much effort or cost. These will be the first features to be removed from scope if the projects timescales are later at risk.•  Wont Haves are features that have been requested but are explicitly excluded from scope for the planned duration, and may be included in a future phase of development.© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  45. 45. ShapeShift•  The integration of the entire planning and development process is the major argument for a dedicated tool. Almost any development process includes activities like: •  Requirements management (product/release backlogs). •  Planning (release/iteration planning). •  Tracking (project/release/iteration progress tracking). •  Quality Assurance (testing, bugs management). •  Feedback Gathering (feedback from customers, ideas, issues).© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  46. 46. AgendaDo We Need Another Agile Tool?BackgroundChallengeWhy Jira?Make Jira AgileIntegration In An Open Agile SuiteQuestions© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  47. 47. Integration in an Agile Suite•  ShapeShift in the first module of a suite of inter- cooperating plugins devoted to bring a complete set of tools for: •  Agile Teams •  Agile Executives •  Agile PMOs•  The suite will Process Tracking•  Manage portfolio as well as economics© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  48. 48. Integration in an Agile Suite“A trend that will continue to influence software tools is ever-tightening release cycles. Where releases once took years, an increasing number of software products will release new functionality to production monthly, week, daily, or even more frequently. […] The trend towards support more frequent transitions between activities will continue. More activities will be supported without large changes of context.”—Kent BeckAgile project management tools have a short history. It is obvious that current tools are just a first tryand they will evolve in the future. Currently three main trends may be mentioned.Tangible – intangible linkageObviously, teams like tangible tools and agile software tools will use something tangible to providebetter user experience. Large sensor displays like Microsoft surface(http://www.microsoft.com/surface/index.html) will be used for iteration planning, daily meetings, andother interactive meetings.Complete integrated development life-cycle solutions© 2008 Pro-netics S.p.A.Agile project management software is evolving into complete life-cycle solutions.The information contained herein is subject to change without notice
  49. 49. AgendaDo We Need Another Agile Tool?BackgroundChallengeWhy Jira?Make Jira AgileIntegration In An Open Agile SuiteQuestions© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  50. 50. Questions & Answers© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  51. 51. © 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  52. 52. © 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  53. 53. © 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  54. 54. © 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  55. 55. © 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  56. 56. © 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice
  57. 57. Thanks f.armani@armaniconsulting.com massimiliano.dessi@pro-netics.com© 2008 Pro-netics S.p.A.The information contained herein is subject to change without notice

×