• Save
change management
Upcoming SlideShare
Loading in...5
×
 

change management

on

  • 675 views

 

Statistics

Views

Total Views
675
Views on SlideShare
675
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

change management change management Presentation Transcript

  • Change management and bug tracking, with emphases on using Bugzilla as an example tool
    By Ian Vaughan
    (detica@ianvaughan.co.uk)
  • Overview
    Explain what is
    A bug
    bug report and
    a bug-tracking system
    Explain the Bug Lifecycle
    Question time
    can also be asked throughout the talk
    2
  • Bug report
    A Bug is a report
    raised
    reported by
    and filled in by stakeholders of a system
    A Bug is
    anything that needs a conclusion recorded
    3
  • Bugzilla
    Bug-tracking system
    Web based front end
    SQL database backend
    4
  • Bugzilla
    Open source software (OSS)
    Mozilla Public License
    Released in 1998
    Still actively developed
    Version 4.0 just released in Feb 2011
    5
  • Why Bugzilla
    Alternatives :-
    Email
    Excel
    COTS
    Bugzilla :-
    Free
    Configurable
    Customisable
    6
  • Why Bugzilla
    Advantages :-
    powerful search
    email notifications
    change history
    many reporting options
    Disadvantages :-
    Free-form text description field
    7
  • Bug Lifecycle
    8
  • Find/discover bug
    Found a problem?
    Using latest release?
    Always search first
    Avoids duplication
    9
  • Simple Search
    10
  • Search Results
    11
  • New bug fields
    Product
    Component
    Version
    Summary
    Description
    12
  • Other fields
    Severity
    Blocker / Critical
    Major
    Normal
    Minor
    Trivial / Enhancement
    Hardware & OS
    13
  • Raise new bug
    14
  • Actioningnew bugs
    Bug gets assigned to someone
    They get emailed
    They decide what should be done
    Will set it as Assigned, and set the
    Target Milestone
    Priority
    15
  • Assigned
    Active / In-progress
    More information might be required
    Gets fixed “Resolved”
    Comments added stating the Changes made
    16
  • Resolved
    Fixed
    Invalid
    Wontfix
    Duplicate
    Worksforme
    17
  • Verified
    Very important stage
    Validates everything done
    Tested
    18
  • Reopened
    Reassigned back to the engineer that stated it was Fixed
    The Fixed-Reopened loop can continue
    19
  • Closed
    Final state of the bug lifecycle
    A record of what was raised and fixed for reporting and historical searches
    20
  • Conclusion
    I have covered :-
    What a bug and bug report is
    What Bugzilla is, and
    A basic overview of how it works
    A bug Lifecycle, and how it relates to Bugzilla
    Any questions?
    21
  • Sources
    http://www.bugzilla.org
    http://en.wikipedia.org/wiki/Bugzilla
    http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems
    http://en.wikipedia.org/wiki/Bug_tracking_system
    http://en.wikipedia.org/wiki/Open_source_software
    http://www.bugzilla.org/docs/
    https://landfill.bugzilla.org/
    22
  • Thank you
    Contact: Ian Vaughan
    detica@ianvaughan.co.uk
    23