View
36
Download
2
Category
Tags:
Preview:
DESCRIPTION
Northeast Wisconsin Agile Users Group. Welcome! Enjoy the Food – Meeting Starts at 6 pm. May 24, 2012 . Our Sponsors Tonight. Fox Valley Technical College - Facilities Skyline Technologies, Inc – Food, Web-site, and Staff, etc.. Thank You! . Agenda. Location and Driving Instructions: - PowerPoint PPT Presentation
Citation preview
Northeast Wisconsin Agile Users Group
May 24, 2012
Welcome!
Enjoy the Food – Meeting Starts at 6 pm
Our Sponsors Tonight
Fox Valley Technical College - FacilitiesSkyline Technologies, Inc – Food, Web-site,
and Staff, etc..
Thank You!
Agenda5:30 p.m. – 6:00 p.m. Welcome and Registration
Pizza and DrinksNetworking
B. Schommer, D. Kinchen
6:00 p.m. – 8:00 p.m. 6:00 – 6:156:15 – 6:306:30 – 6:456:45 – 7:007:00 – 7:157:15 – 7:307:30 – 7:457:45 – 8:00
Agile Tool Review Tool Overview and Group Discussion
Agilezen/TFSFog BugzRallyManual/ No ToolUrban Turtle/TFSTelrik/TFSJIRA
Moderator: S. Hackl M. Wheeler (Solid Consulting)K. Bliek (ZyQuest)B. Schommer (Skyline Tech.)B. Schommer (Skyline Tech.)M. Kuphal (JJ Keller)G. Levenhagen (Skyline Tech.)E. Barnes (KC)
8:00 p.m. – 8:15 p.m. Wrap-up Presentation topic for next meetingMember Feedback
AllB. Schommer
Location and Driving Instructions:http://www.fvtc.edu/public/content.aspx?ID=1340&PID=1
Tool Overview & Discussion • Planning• Sprint/Iteration Task Board• Ease of Updating (i.e. Remaining Hours)• Burndown & Reporting Capabilities• Team Collaboration
Fog Bugz (Presenter: K. Bliek)
PlanningPros Cons
Addition of Cases and Sub-Cases is easy, can add multiple easily
Cannot Drag and Drop
Easy to group by multi-select of cases and then choosing or creating a new milestone
Ordering is based on filter setup, can be tedious
Clearly depicts the hierarchy of case to subcase and which Milestone they are active in
Cross project resource planning is not great
Group edit functionality Cases cannot have more than one resource assigned – would like for “Meetings” or “Analysis” tasks.
Filters are configurable as Tables, Charts
View of future hours is more difficult, better at what has happened (i.e. defects)
Fog Bugz (Presenter: K. Bliek)
Sprint/Iteration Task Board
Pros Cons
Filters can be set up and shared with others to see the data you want
Hierarchy can appear cluttered depending on the filter chosen
Hierarchy of tasks is defined
Fog Bugz (Presenter: K. Bliek)
Ease of Updating (i.e. Remaining Hours)
Pros Cons
Update of remaining hours can be done in-line, do not have to open the ticket to do this
Update of status or other information requires too many clicks and a refresh to display the data.
Fog Bugz (Presenter: K. Bliek)
Burndown & Reporting Capabilities
Pros Cons
API’s exist to develop additional reports
Burndown is hard to read
Fog Bugz (Presenter: K. Bliek)
Team Collaboration
Pros Cons
Integration with multiple tools to capture screen captures and mock-ups (SnagIt/Balsamiq)
Email notification is available
Email response is sent directly to the case to maintain the conversation thread.
Rally (Presenter: B. Schommer)
Planning
Pros Cons
Can plan stories, iterations and releases
Clumsy to move stuff around
Import/export (CSV and XML) Confusing prioritization – especially within parent stories
Drag and drop estimation board Difficult to navigate with large numbers of stories
Poor enterprise resource management
Rally (Presenter: B. Schommer)
Planning
Rally (Presenter: B. Schommer)
Planning
Rally (Presenter: B. Schommer)
Planning
Rally (Presenter: B. Schommer)
Sprint/Iteration Task Board
Pros Cons
Task board view with drag/drop allows hours update
Double click to open task inline for edit
Iteration status view provides a good overview of sprint
Open story/task for edit to update columns not displayed inline
Can flag “blockers”
Allows splitting of stories not completed
Smaller number of user stories makes iteration planning easier.
Rally (Presenter: B. Schommer)
Sprint/Iteration Task Board
Rally (Presenter: B. Schommer)
Sprint/Iteration Task Board
Rally (Presenter: B. Schommer)
Ease of Updating (i.e. Remaining Hours)
Pros Cons
Import/export (CSV and XML) Double click to edit inline
Team member view Deleting stories is a hassle
Can update hours on task board (new window)
Moving stories around (e.g. between epics) is cumbersome
Views are extremely configurable Enhancing some views requires technical expertise
Rally (Presenter: B. Schommer)
Ease of Updating (i.e. Remaining Hours)
Rally (Presenter: B. Schommer)
Burndown & Reporting CapabilitiesPros Cons
Reporting is probably Rally’s strongest feature
Requires some technical expertise
Catalog of available reports
Rally (Presenter: B. Schommer)
Burndown & Reporting Capabilities
Rally (Presenter: B. Schommer)
Team Collaboration
Pros Cons
Provides a Quality tool for tracking test cases and defects
Navigation and data entry is slow for real-time use in meetings
Configurable home page
Good for sharing with remote teams
Good search
Manual/No Tools (Presenter: B. Schommer)
Pros Cons
Encourages involvement by all team members
Becomes more difficult with more stories
“Hands on” Introduces challenges for collaborating with remote team members
Highly visible
Simple
Manual/No Tools (Presenter: B. Schommer)Planning
From: “Scrum and XP from the Trenches” by Henrik Kniberg
Manual/No Tools (Presenter: B. Schommer)
Sprint/ Iteration Task Board
From: “Scrum and XP from the Trenches” by Henrik Kniberg
Manual/No Tools (Presenter: B. Schommer)
Team Collaboration
From: “Scrum and XP from the Trenches” by Henrik Kniberg
Urban Turtle/TFS (Presenter: M. Kuphal)
Planning Board Example
Urban Turtle/TFS (Presenter: M. Kuphal)
Planning
Pros Cons
Drag/Drop Prioritization Limited info to view on planning board (number of fields, etc.) But can drill down to get info needed.
Quick Add Task to User Story Association
Web Based, so screen refreshes/etc can be slow at times.
Drag/Drop Hierarchy Association
Multiple Filter options
Delivers quick access to all info needed during User Story Grooming / Picking sessions
Urban Turtle/TFS (Presenter: M. Kuphal)
Sprint/Iteration Task Board
Urban Turtle/TFS (Presenter: M. Kuphal)
Sprint/Iteration Task Board
Pros Cons
Simple Remaining Work Hours Update on screen
Web Based, so screen refreshes/etc can be slow at times.
Drag/Drop from Status to Status
Auto RWH to zero when moved to Done status
Multiple filtering/card size options
Column number customizable (allowing for KanBan, others)
Task traceability down to ChangeSet.
Urban Turtle/TFS (Presenter: M. Kuphal)
Ease of Updating (i.e. Remaining Hours)
Pros Cons
Covered on Sprint/Iteration Task board.
Urban Turtle/TFS (Presenter: M. Kuphal)
Burndown & Reporting Capabilities
What happened here?
Urban Turtle/TFS (Presenter: M. Kuphal)
Burndown & Reporting Capabilities
Pros Cons
Excellent/Real Time Hours and Story point Burndown charts
Limited ‘out of the box’ Agile based Reporting. (Can create many reports though via queries/etc.)
Urban Turtle/TFS (Presenter: M. Kuphal)
Team Collaboration
Urban Turtle/TFS (Presenter: M. Kuphal)
Team Collaboration
Pros Cons
TFS in General has SharePoint integration (and template project site)
No Chat/IM features
Visual Studio integration
Can be setup to allow public access
This tool combo in general, is built about collaboration while planning and executing a sprint. It allows for visual planning via the Planning board, and point in time User Story/Task status via Task board.
Secondary note: If you use TFS for source control and build/deployment activities, you have a highly integrated, traceability tree from User Story down to deployed build and back up.
Telerik/TFS (Presenter: G. Levenhagen)Planning
Pros Cons
Supports Drag-n-Drop May need to create custom queries for work items
Stage changes before Commit
Plan in Sessions
Can easily link between Work Items
Filtering, Grouping, Aggregation
“New by Example”
Telerik/TFS (Presenter: G. Levenhagen)
Sprint/Iteration Task Board
Pros Cons
Fully functional Iteration control
Fully functional Area control
Built in Task Board
Print Work Item Cards
Filter by Iteration/Area in a Tree
Type ahead search for Items
Telerik/TFS (Presenter: G. Levenhagen)
Ease of Updating (i.e. Remaining Hours)
Pros Cons
Better User Experience than TFS Only 2 time fields (template specific)
Operates against TFS database
Grouped changes
Can customize fields as needed
Copy/Paste for Updates
Telerik/TFS (Presenter: G. Levenhagen)
Burndown & Reporting Capabilities
Pros Cons
Integrates with TFS Reports Nothing built into the tool itself
Telerik/TFS (Presenter: G. Levenhagen)
Team Collaboration
Pros Cons
Integrates with TFS Collaboration Features
Nothing built into the tool itself
JIRA (Presenter: E. Barnes)
Planning
Pros Cons
Easy drag and drop functionality on planning board
Can not sort on different columns
Various views • Hierarchical views • List views
Web based, so you see page by page of information
Views are configurable Difficulty in creating relationships between EPICs and Stories
Can see Tasks in relationship to Story
Points from tasks do not automatically roll up to story/EPIC
Planning Board
JIRA (Presenter: E. Barnes)
Sprint/Iteration Task Board
Pros Cons
Can drill in to the individual user level
No tracking of blockers other than status
Customized dashboards No connection or traceability to code and/or source control
Highly customizable story/task workflows
Activity stream – history of changes
Drag and Drop to advance to next status
Highly customizable story/task workflows
Chart Board
JIRA (Presenter: E. Barnes)
Ease of Updating (i.e. Remaining Hours)
Pros Cons
Decent Dashboard capabilities to drill into and edit items
We don’t capture ETC’s for a Story
Does have email notification that are configurable based on action
Certain fields cannot be searched on. Like, show me all stories that were entered by X. Captured in History, but can’t search
Can Export to Excel
Dashboard for Editing
JIRA (Presenter: E. Barnes)
Burndown & Reporting Capabilities
Pros Cons
Created automatically for planned iterations
No Gantt charts, which some users would like to have
Burndown at any of the Sprint Levels. (May vs. Q2, etc.)
Iteration Burndown by story points versus remaining work
Burndown
JIRA (Presenter: E. Barnes)
Team Collaboration
Pros Cons
Records are not locked while being updated
Depending on security setup, anyone can make changes
Full visibility to all users No chat or IM features
Anyone on the team can update records
No visibility or access by vendor or non company employees – because of our instance
Interactive Planning Board used for Iteration/Sprint planning
Interactive Task Board used during iteration and at daily stand up
Has Cloud capability for sharing outside of the company
Recommended