
Ron Ijack
VP Technology
Upstream Works Software
location_on Canada
Member since 4 years
Ron Ijack
Specialises In (based on submitted proposals)
Senior software and web development professional with over 15 years experience and a proven track record of delivering complex, large-scale projects on time and on budget. Specialist in people and project management, agile development, and web technology. Currently managing large development team consisting of developers, architects and QA analysts in charge of Upstream Works Software call centre software product
-
keyboard_arrow_down
Why we got rid of SCRUM to become agile again
40 Mins
Experience Report
Intermediate
Agile is not about doing scrum, kanban, lean or any other flavour of the process. An organization cannot be “doing” agile, they must “be” agile. They must believe in and understand the agile principles. After going through a successful agile transformation and running scrum for 3 years we realized that it’s just not working for us anymore. The team was suffering from scrum fatigue. It felt like there was a sprint planning, stand up or retrospective meeting happening all the time. We decided to take a hard look at how we were working and turn it on its head. We looked at all the different agile options such as scrum, kanban, lean, xp, etc and decided to take the best part from all of these instead of sticking with one approach. This session will take you through our journey and share what worked for us that could also work in your organization.
-
keyboard_arrow_down
Why we got rid of SCRUM to become agile again
45 Mins
Talk
Advanced
Agile is not about doing scrum, kanban, lean or any other flavour of the process. An organization cannot be “doing” agile, they must “be” agile. They must believe in and understand the agile principles. After going through a successful agile transformation and running scrum for 3 years we realized that it’s just not working for us anymore. The team was suffering from scrum fatigue. It felt like there was a sprint planning, stand up or retrospective meeting happening all the time. We decided to take a hard look at how we were working and turn it on its head. We looked at all the different agile options such as scrum, kanban, lean, xp, etc and decided to take the best part from all of these instead of sticking with one approach. This session will take you through our journey and share what worked for us that could also work in your organization
-
keyboard_arrow_down
Why we got rid of SCRUM to become agile again
45 Mins
Talk
Advanced
Agile is not about doing scrum, kanban, lean or any other flavour of the process. An organization cannot be “doing” agile, they must “be” agile. They must believe in and understand the agile principles.
After going through a successful agile transformation and running scrum for 3 years we realized that it’s just not working for us anymore. The team was suffering from scrum fatigue. It felt like there was a sprint planning, stand up or retrospective meeting happening all the time.
We decided to take a hard look at how we were working and turn it on its head. We looked at all the different agile options such as scrum, kanban, lean, xp, etc and decided to take the best parts from all of these instead of sticking with one approach. This session will take you through our journey and share what worked for us that could also work in your organization.
-
keyboard_arrow_down
The 4 W's of Agile Product Delivery
45 Mins
Talk
Intermediate
Discuss the concept of The 4 W's of agile product delivery in order to help with estimating and projecting product releases while working in an agile environment. The 4 W's are the "Why", "What", "When" and "Who" which are the variables product owners and other stakeholders can manipulate in order to determine the release date and content.
Not all software can be released continuously. As much as we try to avoid it, long term release planning is still necessary in some environments. This session will talk about a new concept of using the 4 W's methodology to add transparency, predictability and collaboration when it comes to long term release planning
-
keyboard_arrow_down
The 4 W's of Agile Product Delivery
60 Mins
Talk
Intermediate
Discuss the concept of The 4 W's of agile product delivery in order to help with estimating and projecting product releases while working in an agile environment. The 4 W's are the "Why", "What", "When" and "Who" which are the variables product owners and other stakeholders can manipulate in order to determine the release date and content.
Not all software can be released continuously. As much as we try to avoid it, long term release planning is still necessary in some environments. This session will talk about a new concept of using the 4 W's methodology to add transparency, predictability and collaboration when it comes to long term release planning
-
No more submissions exist.
-
No more submissions exist.