Practical data science for agile teamsSergey Shishkin
schedule 10 months agoSold Out!
Data science is a misnomer because data is at foundation of any science. However many teams striving for agility lack scientific method and are prone to witchcraft and charlatanism, trying to replicate anecdotes of successful agile transformations. I'm sure as an industry we can do better. We have many sources of data describing our work. If used wisely, the data can provide insights into the trends and health of the change process. Data can also give grounded evidence of areas worth focusing improvement on.
In this session we will review what data is available to the teams today inside the well-known systems of record (issue tracking, source control, CI etc.) and what data is worth starting to collect. We will see how to combine multiple data sources together and present the insights in a meaningful way, that tells a story. We will learn how to look for patterns in data and how to tell if those patterns are real.
For example, a source control system "knows" what files change most frequently and who changed which files (and even lines of code). Combined with the issue tracker data, it can tell you the ratio of "lines spent" between bugs and features or if your "effort per feature" is trending up or down. Now you can measure your technical debt per feature area or system module!
Come and learn what story can your team's data tell you and where to focus your continuous improvement effort.
Beyond User Stories : Take Your Team to Next Level of Awesome!!!Kalpesh Shah
schedule 1 year agoSold Out!
Great teams make great products, but what fuels this greatness? It's the common understanding and passion for the product but more importantly the singularity of purpose and the feedback loop and how the users are responding to the teams work.
The new world of product development is no longer about scope management and delivering the project on time and within budget but it's now more about hypothesis validation and learning from the users and their behaviors.
The dynamics of product development is changing. As more and more organizations are moving towards maturing their agile software development approach the traditional barriers of roles are being broken creating new opportunities and fostering a shift in the mindset. Instead of being tied down to scope management and delivering the project on time, Agile teams are focused and inspired by hypothesis validation and learning from the users and their behaviors.
In this case study we will go over how a portfolio of 12 SCRUM Teams adopted a more outcome approach and how they shifted their mindset from project delivery in Agile way to adopting the Experiment-Measure-Learn-Repeat loop which plays a crucial role in teams overall motivation, performance and moved from being SCRUM Teams to "Product Teams".
We will also see how we experimented with different team formats and how exposing the team members to different events and user research changed the way they perceived the information of the problem they were solving via features and user stories.