Commitment to Continuous Delivery It's a BIG deal! Join Travis Wright as he explains our Commitment to Continuous Delivery, including: -Exciting changes to our current software delivery schedule -New features, products, and fixes, delivered with continuous innovation -Sprint releases for customers who want the latest as soon as it's available -Our quarterly update schedule continued for 2015 -The benefits of getting access to updates at your preferred pace

1. Travis Wright
Director of Product Management
@radtravis
travis.wright@cireson.com
Continuous Innovation and Delivery

2. Agenda
What do we mean by ‘Continuous Innovation’?
What does the roadmap ahead look like?

3. Agile Software Development
Source: http://www.agilenutshell.com/

4. Iterative Development
“Iteration” == “Sprint”
A “story” is a complete end-to-end set of functionality that fills a user need
Example: As an asset manager I want to view a dashboard chart that shows
me the install counts of each of our software titles as a bar chart”
Feature request SRs  Stories

5. Continuous Delivery
Releases
Quarterly Release (v4)
V3.1
V3.2
V3.3
2 weeks 2 weeks2 weeks
…
v3
V3.4
2 weeks
V3.5
2 weeks 2 weeks

6. New Install
Releases
Quarterly Release (v4)
V3.1
V3.2
V3.3
2 weeks 2 weeks2 weeks
…
v3
V3.4
2 weeks
V3.5
2 weeks 2 weeks

7. Upgrade from v3 (supported)
Releases
Quarterly Release (v4)
V3.1
V3.2
V3.3
2 weeks 2 weeks2 weeks
…
v3
V3.4
2 weeks
V3.5
2 weeks 2 weeks

8. Upgrade from v3 (unsupported)
Releases
Quarterly Release (v4)
V3.1
V3.2
V3.3
2 weeks 2 weeks2 weeks
…
v3
V3.4
2 weeks
V3.5
2 weeks 2 weeks
STOP

9. Upgrade from v3 (unsupported)
Releases
Quarterly Release (v4)
V3.1
V3.2
V3.3
2 weeks 2 weeks2 weeks
…
v3
V3.4
2 weeks
V3.5
2 weeks 2 weeks
STOP

10. Upgrade from v2 to a sprint release
(unsupported)
Releases
Quarterly Release (v4)
V3.1
V3.2
V3.3
2 weeks 2 weeks2 weeks
…
v3
V3.4
2 weeks
V3.5
2 weeks 2 weeks
STOP
v2

11. Bugs
Time will be allocated each sprint to work on bugs
reported by customers/partners
Bugs will be worked on in priority (impact X urgency)
order and generally FIFO
Generally… Unless a bug is very large it will be fixed
in the same sprint it is reported in if it is reported in
the first week of the sprint. If it is reported in the
second week of the sprint it will be fixed in the next
sprint.

12. Hotfixes
Bug criteria:
• Security issue
• Data loss
• No workaround
• Major feature not working for all customers
• Prevents upgrade to next version or side-by-side deployment
Hotfixes will be released as soon as possible
Customers will be notified of availability via email and announcement
Fixes will be rolled into the next sprint release
Download from https://support.cireson.com/software

13. Change is Constant
No more beta cycles
Major new features/apps will be disabled by default or only
visible to administrators
Preproduction acceptance testing is essential
Localization will be completed by 3.2. Will stay closely in sync.
Each sprint release will be deployed to Cireson Support Portal
first! #Dogfood 

14. Schedule
Version Release Date
3.1 Nov 21
3.2 Dec 5
3.3 Dec 19
3.4 Jan 2
3.5 Jan 16
3.6 (v4?) Jan 30

15. Reminders
• We are hiring! Dev, test, PM, consultants, sales, support
• Upcoming events:
• Experts Live – Netherlands (Next week!)
• System Center Universe – Dallas (February)
• Nordic Infrastructure Conference – Oslo (February)
• Ignite – Chicago (May)

16. Travis Wright
travis.wright@cireson.com
@radtravis
@teamcireson
More info
team@cireson.com
We’re here to help!