ݺߣ

ݺߣShare a Scribd company logo

Release andconfigurationmanagementfreenest1dot4

•
•
JAMK
JAMK

Ubuntu relies heavily on community testing during release development. Volunteers help test daily builds and report bugs. As release dates near, testing intensifies with "test drives" of the final release candidate version. The final release undergoes extensive testing in a dedicated testing period before it is made available to all users. Automated testing systems also help validate releases. Overall, Ubuntu exemplifies how open source projects can benefit from crowd-sourced testing by engaged community members.

1 of 17
Release andconfigurationmanagementfreenest1dot4
Change Management in context of IFDK reference product
About this course material - This material if for general training for Release and Configuration Management - Material is more supportive in class room - Material will be updated during courses - FreeNest Portable Project Platform is used to demonstrate things only in practice. This is not limiting usage for material for other training environments (I hope ) About
Release & Configuration Management http://en.wikipedia.org/wiki/Configuration_management http://en.wikipedia.org/wiki/Release_management Yläotsikko
Is product a combination of features? Standby Mode Table Drum Mode MIDI Support Calory Counter Touch Screen with single tap Drum Metronome About
Is product a combination of features? Table Drum Mode Standby Mode Calory Counter MIDI Support Core Software Drum Metronome Touch Screen with single tap About
Customer/Business Requirements? Touch Screen with single tap Simple Training Mode Drum Metronome Calory Counter MIDI Support Table Drum Mode Customer Type 1 Customer Type 2 Customer Type 3 Customer Type 4 Who are our target customers?
Customer Strategy Touch Screen with single tap Simple Training Mode Calory Counter Drum Metronome Table Drum Mode MIDI Support Primary Target Secondary Target Customer Type 1 Customer Type 2 Customer Type 3 Customer Type 4 What is our key customer?
Features and release planning TIME TO MARKET!! For Target Group 1 Feature: Simple Training Mode Requirement Requirement USE CASE #1 User Story #1 Requirement Requirement USE CASE #2 User Story #2 Requirement Requirement USE CASE #3 User Story #3 TIME TO MARKET!! For Target Group 2 Feature Touch Screen with single tap CORE/Platform Software Requirement Requirement USE CASE #1 User Story #1 Development Requirement Requirement USE CASE #2 User Story #2 Requirement Requirement USE CASE #3 User Story #3 TIME TO MARKET!! For Target Group 3 Feature: Table Drum mode Requirement Requirement USE CASE #1 Requirement Requirement USE CASE #2 Requirement Requirement USE CASE #3 Release 0.1 Release 1.0 Release 1.1 Release 1.2
Release Planning Discussion? Release Plan - Release Note Roadmap where have you seen this Yläotsikko
Release Management Version Version 0.2 Version 0.3 Version 0.4 Trunk 0.1 Customer Version 0.2.1 Version 0.2.2 Version 0.2.3 1 Customer Version Version Version 1 0.2.2.1 0.2.2.2 0.2.2.3 Yläotsikko
Release & Configuration Managmement Version Version 0.2 Version 0.3 Version 0.4 Trunk 0.1 Release 1.0 Feature s Customer Version 0.2.1 Version 0.2.2 Version 0.2.3 Release 1 1.0 Feature s Customer Version Version Version Release 0.2.2.1 0.2.2.2 0.2.2.3 1 1.0 Feature s Yläotsikko
Testlink & build testing Discussion? Release Plan - Release Note Roadmap where have you seen this Yläotsikko
Validaton& Verificaton (Testing) Management Tested Release/configuration Error/Defect Version 0.4 Report Change Request Test Plan Error/Defect Version Test Report 0.2.2 Cases For Change Features Request Error/Defect Version 0.2.2.2 Report Change Request Yläotsikko
Example of Idealistic Release Plan for large system Unstable Released Edge Unit & Testing Day 1 Day 2 Day … Day 1 Day 2 Day … Day 1 Day 2 Day … Fix Released Integration Testing Quartal Monthly Monthly Monthly Release Release Release Release System Acceptance Stable Released 6 month Release Testing
Traditional SW Project vs Open Source Project Open Source – Crowd Sourcing SW Relase tested without coordination by group of volunteers Release tested by customer Field Testing Test Group Yläotsikko
Discussion Learn how Ubuntu has organized release testing?

More Related Content

Release andconfigurationmanagementfreenest1dot4

  • 2. Change Management in context of IFDK reference product
  • 3. About this course material - This material if for general training for Release and Configuration Management - Material is more supportive in class room - Material will be updated during courses - FreeNest Portable Project Platform is used to demonstrate things only in practice. This is not limiting usage for material for other training environments (I hope ) About
  • 4. Release & Configuration Management http://en.wikipedia.org/wiki/Configuration_management http://en.wikipedia.org/wiki/Release_management Yläotsikko
  • 5. Is product a combination of features? Standby Mode Table Drum Mode MIDI Support Calory Counter Touch Screen with single tap Drum Metronome About
  • 6. Is product a combination of features? Table Drum Mode Standby Mode Calory Counter MIDI Support Core Software Drum Metronome Touch Screen with single tap About
  • 7. Customer/Business Requirements? Touch Screen with single tap Simple Training Mode Drum Metronome Calory Counter MIDI Support Table Drum Mode Customer Type 1 Customer Type 2 Customer Type 3 Customer Type 4 Who are our target customers?
  • 8. Customer Strategy Touch Screen with single tap Simple Training Mode Calory Counter Drum Metronome Table Drum Mode MIDI Support Primary Target Secondary Target Customer Type 1 Customer Type 2 Customer Type 3 Customer Type 4 What is our key customer?
  • 9. Features and release planning TIME TO MARKET!! For Target Group 1 Feature: Simple Training Mode Requirement Requirement USE CASE #1 User Story #1 Requirement Requirement USE CASE #2 User Story #2 Requirement Requirement USE CASE #3 User Story #3 TIME TO MARKET!! For Target Group 2 Feature Touch Screen with single tap CORE/Platform Software Requirement Requirement USE CASE #1 User Story #1 Development Requirement Requirement USE CASE #2 User Story #2 Requirement Requirement USE CASE #3 User Story #3 TIME TO MARKET!! For Target Group 3 Feature: Table Drum mode Requirement Requirement USE CASE #1 Requirement Requirement USE CASE #2 Requirement Requirement USE CASE #3 Release 0.1 Release 1.0 Release 1.1 Release 1.2
  • 10. Release Planning Discussion? Release Plan - Release Note Roadmap where have you seen this Yläotsikko
  • 11. Release Management Version Version 0.2 Version 0.3 Version 0.4 Trunk 0.1 Customer Version 0.2.1 Version 0.2.2 Version 0.2.3 1 Customer Version Version Version 1 0.2.2.1 0.2.2.2 0.2.2.3 Yläotsikko
  • 12. Release & Configuration Managmement Version Version 0.2 Version 0.3 Version 0.4 Trunk 0.1 Release 1.0 Feature s Customer Version 0.2.1 Version 0.2.2 Version 0.2.3 Release 1 1.0 Feature s Customer Version Version Version Release 0.2.2.1 0.2.2.2 0.2.2.3 1 1.0 Feature s Yläotsikko
  • 13. Testlink & build testing Discussion? Release Plan - Release Note Roadmap where have you seen this Yläotsikko
  • 14. Validaton& Verificaton (Testing) Management Tested Release/configuration Error/Defect Version 0.4 Report Change Request Test Plan Error/Defect Version Test Report 0.2.2 Cases For Change Features Request Error/Defect Version 0.2.2.2 Report Change Request Yläotsikko
  • 15. Example of Idealistic Release Plan for large system Unstable Released Edge Unit & Testing Day 1 Day 2 Day … Day 1 Day 2 Day … Day 1 Day 2 Day … Fix Released Integration Testing Quartal Monthly Monthly Monthly Release Release Release Release System Acceptance Stable Released 6 month Release Testing
  • 16. Traditional SW Project vs Open Source Project Open Source – Crowd Sourcing SW Relase tested without coordination by group of volunteers Release tested by customer Field Testing Test Group Yläotsikko
  • 17. Discussion Learn how Ubuntu has organized release testing?