CitconWiki - User contributions [en]

CITCONANZ2013Sessions

2013-03-11T10:19:44Z

Mrako: /* 3:15 Topics */

CITCON ANZ 2013 Sydney Sessions

Back to the [[Main Page]]

== 10:00 Topics ==

# [[MultipleCdDiscussion]]
# DevOps and Testing
# Testing using robots
# Proxy Product Owner
# Testers are an endangered species

== 11:15 Topics ==

# Challenges in writing maintainable acceptance tests
# Improving In Corporate Environments
# [[NoMeansNo]]
# [[ScalingUpCD|Scaling up CD - Case study from telecommunications]]
# [[Testing vs Checking]]

== Lunch Topics ==

# Lean Coffee

== 2:00 Topics ==

# Jeff is angry at silo thinking and DevOps isn't helping
# Testing Lightning Talks
# Distributed automated testing for 300,000+ unit tests
# Ask a vendor anything - Jenkins and Bamboo
# Discussion on increasing automation - how best to deal with legacy code

== 3:15 Topics ==

# Automated Testing of Automated Tests
# ATDD in action - Live demo of automated acceptance testing
# Catharsis
# [[ScalingUpCD|Challenges of testing and deploying at Scale]]
# Selenium Best Practices

== 4:30 Topics ==

# Coding Dojos
# BDD from requirements to acceptance tests / Specification by Example
# How to get started with Continuous Delivery, especially for small teams
# More time for coffee - 5 (soft) steps to CD
# [[PerformanceTestingInAgile]]

== Table View ==

{| class="wikitable"
|-
! #
! 10:00
! 11:15
! 2:00
! 3:15
! 4:30
|-
| Hall of Justice
| Problems adopting Continuous Delivery
| Challenges in writing maintainable acceptance tests
| Jeff is angry at silo thinking and DevOps isn't helping
| Automated Testing of Automated Tests
| Coding Dojos
|-
| TV Lounge
| DevOps and Testing
| Improving In Corporate Environments
| Testing Lightening Talks
| ATDD in action - Live demo of automated acceptance testing
| BDD from requirements to acceptance tests / Specification by Example
|-
| Lunch Corner
| Testing using robots
| No means No - how to keep test failures meaningful
| Distributed automated testing for 300,000+ unit tests
| Catharsis
| How to get started with Continuous Delivery, especially for small teams
|-
| Ping Pong Table
| Proxy Product Owner
| Scaling up CD - Case study from telecommunications
| Ask a vendor anything - Jenkins and Bamboo
| Challenges of testing and deploying at scale
| More time for coffee - 5 (soft) steps to CD
|-
| Pool Table
| Testers are an endangered species
| Testing vs Checking
| Discussion on increasing automation - how best to deal with legacy code
| Selenium Best Practices
| Performance Testing within an agile methodology
|}

ScalingUpCD

2013-03-11T10:18:51Z

Mrako: Created page with "== Introduction == This session was a brief description of a successful transformation from an 8 hour build to a 5 minute reliable feedback cycle. The product has more than ..."

== Introduction ==

This session was a brief description of a successful transformation from an 8 hour build to a 5 minute reliable feedback cycle.

The product has more than 16 million lines of code and more than 350 developers.

The transformation from a monolithic, strongly coupled system architecture took almost two years to merge into a decoupled component build where the feedback loops were taken down to an average of five minutes.

* [http://www.slideshare.net/mrako/five-steps-tocd Slides]
* [http://bambuser.com/v/2649963 Stream from the Turku Agile Day]

== Scaling up ==

=== Envision ===

All change starts from an idea. You should start with a crazy-enough idea, one that you barely believe even yourself.

For this project the vision was simply smaller deliverables, less bugs and better feedback.

=== Enable ===

The bigger the organization the harder it is to introduce new ideas and changes. Earn your respect by enabling something that supports the crazy vision.

In this project we created a tool that understands the network of dependencies between components and with that information can create a parallel build with the correct build order.

=== Communicate ===

Once you have enabled something - tell the people that you know will support you and spread the word.

In this project we received constant support from one Scrum Team that helped us elaborate and develop the tools and simultaneously started spreading the word within the development organization.

=== Deliver Now ===

The less you change people's daily working practices, the better. In a long and determinate project it is best to deliver as often as possible so that people get used to the changes while you are creating new.

=== Iterate ===

Once you have delivered, go back to envisioning and enabling.

CITCONANZ2013Sessions

2013-03-04T10:24:44Z

Mrako: /* 3:15 Topics */

CITCON ANZ 2013 Sydney Sessions

Back to the [[Main Page]]

== 10:00 Topics ==

# [[MultipleCdDiscussion]]
# DevOps and Testing
# Testing using robots
# Proxy Product Owner
# Testers are an endangered species

== 11:15 Topics ==

# Challenges in writing maintainable acceptance tests
# Improving In Corporate Environments
# [[NoMeansNo]]
# [[ScalingUpCD|Scaling up CD - Case study from telecommunications]]
# [[Testing vs Checking]]

== Lunch Topics ==

# Lean Coffee

== 2:00 Topics ==

# Jeff is angry at silo thinking and DevOps isn't helping
# Testing Lightning Talks
# Distributed automated testing for 300,000+ unit tests
# Ask a vendor anything - Jenkins and Bamboo
# Discussion on increasing automation - how best to deal with legacy code

== 3:15 Topics ==

# Automated Testing of Automated Tests
# ATDD in action - Live demo of automated acceptance testing
# Catharsis
# [[ChallengesOfTestingAtScale|Challenges of testing and deploying at Scale]]
# Selenium Best Practices

== 4:30 Topics ==

# Coding Dojos
# BDD from requirements to acceptance tests / Specification by Example
# How to get started with Continuous Delivery, especially for small teams
# More time for coffee - 5 (soft) steps to CD
# [[PerformanceTestingInAgile]]

== Table View ==

{| class="wikitable"
|-
! #
! 10:00
! 11:15
! 2:00
! 3:15
! 4:30
|-
| Hall of Justice
| Problems adopting Continuous Delivery
| Challenges in writing maintainable acceptance tests
| Jeff is angry at silo thinking and DevOps isn't helping
| Automated Testing of Automated Tests
| Coding Dojos
|-
| TV Lounge
| DevOps and Testing
| Improving In Corporate Environments
| Testing Lightening Talks
| ATDD in action - Live demo of automated acceptance testing
| BDD from requirements to acceptance tests / Specification by Example
|-
| Lunch Corner
| Testing using robots
| No means No - how to keep test failures meaningful
| Distributed automated testing for 300,000+ unit tests
| Catharsis
| How to get started with Continuous Delivery, especially for small teams
|-
| Ping Pong Table
| Proxy Product Owner
| Scaling up CD - Case study from telecommunications
| Ask a vendor anything - Jenkins and Bamboo
| Challenges of testing and deploying at scale
| More time for coffee - 5 (soft) steps to CD
|-
| Pool Table
| Testers are an endangered species
| Testing vs Checking
| Discussion on increasing automation - how best to deal with legacy code
| Selenium Best Practices
| Performance Testing within an agile methodology
|}

CITCONANZ2013Sessions

2013-03-04T10:23:23Z

Mrako: /* 11:15 Topics */

CITCON ANZ 2013 Sydney Sessions

Back to the [[Main Page]]

== 10:00 Topics ==

# [[MultipleCdDiscussion]]
# DevOps and Testing
# Testing using robots
# Proxy Product Owner
# Testers are an endangered species

== 11:15 Topics ==

# Challenges in writing maintainable acceptance tests
# Improving In Corporate Environments
# [[NoMeansNo]]
# [[ScalingUpCD|Scaling up CD - Case study from telecommunications]]
# [[Testing vs Checking]]

== Lunch Topics ==

# Lean Coffee

== 2:00 Topics ==

# Jeff is angry at silo thinking and DevOps isn't helping
# Testing Lightning Talks
# Distributed automated testing for 300,000+ unit tests
# Ask a vendor anything - Jenkins and Bamboo
# Discussion on increasing automation - how best to deal with legacy code

== 3:15 Topics ==

# Automated Testing of Automated Tests
# ATDD in action - Live demo of automated acceptance testing
# Catharsis
# Challenges of testing and deploying at scale
# Selenium Best Practices

== 4:30 Topics ==

# Coding Dojos
# BDD from requirements to acceptance tests / Specification by Example
# How to get started with Continuous Delivery, especially for small teams
# More time for coffee - 5 (soft) steps to CD
# [[PerformanceTestingInAgile]]

== Table View ==

{| class="wikitable"
|-
! #
! 10:00
! 11:15
! 2:00
! 3:15
! 4:30
|-
| Hall of Justice
| Problems adopting Continuous Delivery
| Challenges in writing maintainable acceptance tests
| Jeff is angry at silo thinking and DevOps isn't helping
| Automated Testing of Automated Tests
| Coding Dojos
|-
| TV Lounge
| DevOps and Testing
| Improving In Corporate Environments
| Testing Lightening Talks
| ATDD in action - Live demo of automated acceptance testing
| BDD from requirements to acceptance tests / Specification by Example
|-
| Lunch Corner
| Testing using robots
| No means No - how to keep test failures meaningful
| Distributed automated testing for 300,000+ unit tests
| Catharsis
| How to get started with Continuous Delivery, especially for small teams
|-
| Ping Pong Table
| Proxy Product Owner
| Scaling up CD - Case study from telecommunications
| Ask a vendor anything - Jenkins and Bamboo
| Challenges of testing and deploying at scale
| More time for coffee - 5 (soft) steps to CD
|-
| Pool Table
| Testers are an endangered species
| Testing vs Checking
| Discussion on increasing automation - how best to deal with legacy code
| Selenium Best Practices
| Performance Testing within an agile methodology
|}

Marko Klemetti

2013-02-08T00:34:24Z

Mrako: Created page with "'''Marko Klemetti''' is a father of three, a leader and a developer. Marko works as a unit leader in [http://www.eficode.com Eficode], a Finnish company employing more than 1..."

'''Marko Klemetti''' is a father of three, a leader and a developer.

Marko works as a unit leader in [http://www.eficode.com Eficode], a Finnish company employing more than 100 experts. With his team he has ''created'', ''consulted'' and ''coached'' many Continuous Delivery related practices and tools in the Enterprise and Start-up world. Eficode belongs to the core developers of [http://code.google.com/p/robotframework/ Robot Framework] and the latest success story comes from [http://www.rovio.com/ Rovio], [http://www.eficode.com/company/company_news/news_item?id=82 Angry Birds hit automated software production line].

Marko actively writes to [http://mrako.com mrako.com], steadily creating the arc of successful software development in the modern world. He is also the founder of [http://entertrail.com Trail].