Continuous Integration is crucial in modern software development. Therefore, a lot of teams involve Mr. Jenkins and hope for a better quality software. But do they know that they are killing Mr. Jenkins? My talk will answer this question and introduce 3 levels of good practices to maintain a healthy, strong and long living Mr. Jenkins.

 
1 favorite thumb_down thumb_up 1 comment visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Presentation

- Introduce the problem

- Answer the problem by 3 levels of good practices

- Demo

Learning Outcome

- CI Mindset and CI culture

- Internet of Things

- Teamwork's good practices

Target Audience

Developers, team members, managers, team's influencers

Prerequisites for Attendees

No need

schedule Submitted 2 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Madhavi Ledalla
    By Madhavi Ledalla  ~  2 months ago
    reply Reply

    Hi Quang, thank you for your interest in RSGI 2019. This seems to be interesting story around Mr.Jenkins.

    I think the submission could be improved by:

    • Adding some details to 3 levels of good practices that you intend to share
    • Elaborating on "Internet of things" in learning outcome
    • Sharing some challenges that you faced while implementing CI Mindset and CI culture in your organization and  how did you go about handling them and describe the journey of Mr.Jenkins

    Hope you find this feedback helpful.

    Thank you!


    • Liked Amogh Joshi
      keyboard_arrow_down

      Amogh Joshi - As an Agile Executive, I need to support team-level patterns, so that velocity can increase across the board.

      Amogh Joshi
      Amogh Joshi
      cofounder
      Scrumglobal
      schedule 2 weeks ago
      Sold Out!
      90 Mins
      Hands on Session
      Intermediate

      As an Agile Executive, I need to support team-level patterns, so that productivity can increase across the board.

      We will be discussing about the below patterns and see how these can be used to increase productivity of scrum teams.

      • Colocation
      • Small teams
      • Stable teams
      • Dedicated teams
      • Yesterday’s weather - finish early
      • T-shaped people (enables Swarming)
      • Daily Scrum
      • Interrupt buffer
      • Ready backlog
      • Fix bugs within a day
      • All testing completed inside the sprint

      We will also discuss other how identifying patterns makes it easier to win.

      The use of above pattenrs in an scaling framewok and where and how to appy them will be concluded.

      There is a small activity - Learn how to draw, which alos shows the use of same patterns to identify solution to different problems will be done.

      We can manage time if 90 min is not avaialbe.