Difference between revisions of "Continuous Integration Roadmap"

From CitconWiki
Jump to navigationJump to search
(New page: '''CI Roadmap''' The intent of the session was to brainstorm a working maturity roadmap for Continuous Integration. Participants first agreed on maturity as a model - from intro to advance...)
 
Line 1: Line 1:
 
'''CI Roadmap'''
 
'''CI Roadmap'''
 +
 
The intent of the session was to brainstorm a working maturity roadmap for Continuous Integration. Participants first agreed on maturity as a model - from intro to advanced. The idea is to have a sense of CI practices, things you can do with CI. This can be useful when:
 
The intent of the session was to brainstorm a working maturity roadmap for Continuous Integration. Participants first agreed on maturity as a model - from intro to advanced. The idea is to have a sense of CI practices, things you can do with CI. This can be useful when:
  
 
- You are getting started with CI, and you want to know what's possible - what kinds of things can you do with CI,
 
- You are getting started with CI, and you want to know what's possible - what kinds of things can you do with CI,
 +
 
- You have started using CI, and you're trying to evaluate what might be the next value vs. effort thing you could do,
 
- You have started using CI, and you're trying to evaluate what might be the next value vs. effort thing you could do,
 +
 
- You want to sell CI to your organization, and need to give a sense of what can be achieved.
 
- You want to sell CI to your organization, and need to give a sense of what can be achieved.
  
Process:
+
 
 +
'''Process:'''
 +
 
 
- Agree on a continuum model for the discussion - maturity was chosen,
 
- Agree on a continuum model for the discussion - maturity was chosen,
 +
 
- Brainstorm all sorts of tasks and things that can be done with CI and project automation,
 
- Brainstorm all sorts of tasks and things that can be done with CI and project automation,
 +
 
- Brainstorm a set of categories - chosen: Intro, Novice, Intermediate, Advanced, Insane
 
- Brainstorm a set of categories - chosen: Intro, Novice, Intermediate, Advanced, Insane
 +
 
- Group sort tasks to categories - all tasks written on post-its - group came up to the wall and organized tasks under categories. Light discussion - no fistfights.
 
- Group sort tasks to categories - all tasks written on post-its - group came up to the wall and organized tasks under categories. Light discussion - no fistfights.
 +
 
- Group made a pass through the categories - organizing within each category by value, adding missing tasks, shifting tasks across categories as needed.
 
- Group made a pass through the categories - organizing within each category by value, adding missing tasks, shifting tasks across categories as needed.
 +
  
 
The resulting roadmap itself is pretty useful. It should NOT be interpreted as prescriptive. Another critical observation from participants was that our concept of CI has matured in recent years. The tasks represented were as much about project automation/efficiency as they were CI. Do we need a new name for CI? Project Automation? Lifecycle Automation?  
 
The resulting roadmap itself is pretty useful. It should NOT be interpreted as prescriptive. Another critical observation from participants was that our concept of CI has matured in recent years. The tasks represented were as much about project automation/efficiency as they were CI. Do we need a new name for CI? Project Automation? Lifecycle Automation?  
Line 20: Line 30:
  
 
Notes TBD:
 
Notes TBD:
 
 
 
 
Notes and Roadmap diagram coming soon...
 

Revision as of 10:01, 25 April 2009

CI Roadmap

The intent of the session was to brainstorm a working maturity roadmap for Continuous Integration. Participants first agreed on maturity as a model - from intro to advanced. The idea is to have a sense of CI practices, things you can do with CI. This can be useful when:

- You are getting started with CI, and you want to know what's possible - what kinds of things can you do with CI,

- You have started using CI, and you're trying to evaluate what might be the next value vs. effort thing you could do,

- You want to sell CI to your organization, and need to give a sense of what can be achieved.


Process:

- Agree on a continuum model for the discussion - maturity was chosen,

- Brainstorm all sorts of tasks and things that can be done with CI and project automation,

- Brainstorm a set of categories - chosen: Intro, Novice, Intermediate, Advanced, Insane

- Group sort tasks to categories - all tasks written on post-its - group came up to the wall and organized tasks under categories. Light discussion - no fistfights.

- Group made a pass through the categories - organizing within each category by value, adding missing tasks, shifting tasks across categories as needed.


The resulting roadmap itself is pretty useful. It should NOT be interpreted as prescriptive. Another critical observation from participants was that our concept of CI has matured in recent years. The tasks represented were as much about project automation/efficiency as they were CI. Do we need a new name for CI? Project Automation? Lifecycle Automation?


Roadmap Diagram TBD:


Notes TBD: