• Liked Pramod Sadalage
    keyboard_arrow_down

    Ten Patterns of Database Refactoring

    Pramod Sadalage
    Pramod Sadalage
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Over the life of an application as requirements change, application usage patterns alter, load and performance changes the need to change database and database architecture is inevitable. There are patterns of these changes such as

    1. 1. Encapsulate Table with View
    2. 2. Migrate method from database
    3. 3. Replace method with views
    4. 4. Introduce Read only table
    5. 5. Split table
    6. 6. Make column non-nullable
    7. 7. Drop column
    8. 8. Add foreign key constaint
    9. 9. Merge columns
    10. 10. Replace columns

    In this talk we will discuss the above database refactoring patterns and different implementation techniques to enable blue, green deployments, allow for legacy applications to work with fast changing database and enable the teams to effectively refactor the database to fulfill the changing needs of the organization.

  • Liked Johannes Brodwall
    keyboard_arrow_down

    Practice agile programming with coding dojo

    Johannes Brodwall
    Johannes Brodwall
    Buddhima w.wickramasinghe.
    Buddhima w.wickramasinghe.
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    A Coding Dojo is a fun and social way to become a better programmer. Johannes is an experienced coding coach who will guide you through a few hours of programming that will transform your understand your craft and yourself as a programmer. In the workshop you get to try out pair programming, test-driven development and continuous refactoring for yourself and you get lots of recommendations on how to improve your coding and testing. You will need to bring your own computer with a development environment of your choice. Recommended for Java, Ruby, JavaScript and C# developers.

    This is what previous participants say about the workshop:

    • What did you learn? New tools, pair programming and fun exercises; Ide tricks, programming language basics, testing tools, using tests as a reasoning tool; you can comfortably pair with strangers.
    • What surprised you? Small steps work better than planning; It's easy to get started when you pair program; Pair programming is nice
    • What do you plan to do next? Using TDD every day; Listen to partner more carefully - he may already have solved the problem.
  • Liked Ellen Grove
    keyboard_arrow_down

    Build Your Dreams: User Requirements Gathering with LEGO Serious Play

    Ellen Grove
    Ellen Grove
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    Let your hands be the search engine for your brain! LEGO® Serious Play® is a powerful thinking, communicating and problem solving technique that can help you and your team do serious work through structured play activities using a popular and playful 3D modeling toy. Through a facilitated process of building models that, storytelling and reflection, every person at the table is engaged and actively participating in the discussion, whether the topic is individual aspirations, team relationships, developing a new product or solving a wicked organizational problem. Everyone builds and everyone tells their story – all participants have equal opportunity to put their own points of view on the table, unlocking new perspectives and exposing the answers that are already in the room.  LEGO Serious Play has been used successfully for team-building and problem solving in a variety of organizations, from NASA to RBC to academic settings and public utilities.  

    This presentation provides a hands-on introduction to LEGO Serious Play, so that you can experience firsthand how using LEGO to do real work unleashes creativity and enables meaningful conversations in a very short time. We will explore how to use this playful technique to collaboratively elicit information about user requirements and strategic design issues using the open source User Requirements with Lego methodology developed by a team at the University of Lugano, Switzerland.  This approach is particularly suited to Agile teams that want to get team members and stakeholders sharing their different perspectives on common goals in an open and light-weight manner.

  • Liked Mukesh Bhangria
    keyboard_arrow_down

    Continuous Refactoring at Amazon: A Case Study

    Mukesh Bhangria
    Mukesh Bhangria
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Between the project deadlines, we always feel there is code which needs to be improved

    Usually Developers have the following 3 options:

    - Bite the bullet and do the refactoring as they go along.
    - Park the issue and address it later.
    - Allocate special time when the project gets out-of-control.

    As customer facing stories take higher priority, usually Developers are forced to choose the last option.

    However a team at Amazon took a different approach. Attend this session to listen to their first-hand story of how they changed this typical behavior to achieve Continuous Deployment on a critical service.

  • Liked Sreerupa Sen
    keyboard_arrow_down

    Changing our Rhythm: Our Ongoing Journey towards Continuous Delivery

    Sreerupa Sen
    Sreerupa Sen
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Annual software release cycles cramping the agility of the team? Too many hot fixes reducing the efficiency of your organization? Customers waiting impatientlyfor  the next cool features hot off the press? These are some of the painful and common problems faced by development teams worldwide. In today's world, most things get outdated or out-of-fashion very fast - and software is no different. Users cannot afford to wait for the next cool set of features for a year. They want a steady stream of cool new features that they can adopt and use immediately.

    My team follows a development model that we like to call Open Commercial Development - where we're always connected to our stakeholders, our plans are out in the open, and we're always gathering feedback and reprioritizing. We used to have yearly releases of our product - a sort of big bang release with a host of new featres. Based on our stakeholder interactions, however, we figured that our software delivery wasn't agile enough for our customers. Users wanted new features incrementally throughout the year. They especially didn't want to wait a year for a feature that they'd requested that was critical for their business.

    So began our journey to Continuous Delivery - an interesting one for sure. It's not easy to deliver new features, manage technical debt, collaborate with users and incorporate their feedback into the new features - once every quarter. To do it consistently, with quality and on time, you need to have a framework in place - a combination of planning, process, automation and team organization - that lets teams focus on the right things to get to DONE DONE for their new features, and at the same time manage their quality and tecnical debt. Over the past year, we like to think that we've put that framework in place, and that is what I'd like to talk about in this session.

  • Liked Ryan Martens
    keyboard_arrow_down

    Beyond Agile Execution: Agility for Business and Impact

    Ryan Martens
    Ryan Martens
    schedule 3 years ago
    Sold Out!
    60 mins
    Keynote
    Beginner

    Agile is not just a process change, its a mindset change for most. With faster time to market, better feedback and highly functioning teams, the Agile mindset opens our eyes to a better way of working as humans on large complicated and complex problems. Combining it with the concepts of Lean Startup, delivers another leap in team capacity and capabilities. It also opens the possibilities of using agility for more than just software development.

    Do you wonder how can we drive innovation in a disciplined way to tame our world's toughest problems? Can we apply the lessons learned from Agile and Lean Startup? Over the past three years, we've been able to apply agility at a new level, beyond business impact. Through our corporate social responsibility effort, "Rally for Impact", we aim to apply the agile mindset to mobilize citizen engineers to serve our communities and protect the planet. I want you to consider this growth path for yourself and your agile teams.

    Let's open the worlds mindset to a better way to empathize, explore and execute in these complex times.

  • Liked Tathagat Varma
    keyboard_arrow_down

    Designing agile feedbacks for agile learning - an experience report

    Tathagat Varma
    Tathagat Varma
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Feedback is perhaps the most important aspect of the overall agile lifecycle. If the feedback is too wide and shallow, it won't give enough actionable feedback. If it is too narrow and deep, it might fail to register feedback outside its focus area. So, how does one go about designing feedbacks that enable agile learning. We call them agile feedbacks.

    In this brief session, we will share an experience from designing agile feedbacks for agile trainings and workshops. The objective was to get most critical feedback in shortest amount of time to enable quick action planning. We created feedback that took a maximum of 5 minutes and enabled the most important learning in both, focussed as well as open-ended manner that allowed us to focus on the most critical items. We employed elements of Design Thinking and Rapid Iterative Testing and Evaluation (RITE) to improve the process and quality of feedback themselves. We will also be touching up these concepts and how effective they were.

  • Liked Richard Kasperowski
    keyboard_arrow_down

    Self-management and Self-organization: Agile Games with Motion

    Richard Kasperowski
    Richard Kasperowski
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    Self-management and self-organization are important themes in Agile software development, but what do they actually look like?  We pontificate about worker empowerment, but then we revert to command-and-control: our product owners mandate project scope and deadlines, and our Scrum Masters assign tasks to team members.  Why can’t we let teams be self-organized and workers be self-managed?
     
    These activity-based learning activities are kinesthetic learning games.  Players learn by playing fun, physical games of movement.  These games create a social atmosphere and a full body and mind experience that make it easy and fun to learn.  We’ll play five games, including Line Up, 60 Paces, Triangles, Human Knot, and a special surprise game.
     
    In this session, we explore and experience self-management and self-organization via Agile games.  You will leave with a deep internalized understanding of self-management and self-organization and an appreciation of how they work better than command-and-control.  You’ll be able to share these games with your coworkers.

  • Liked Howard Deiner
    keyboard_arrow_down

    Pivoting Your Organization to Become Agile Testers

    Howard Deiner
    Howard Deiner
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Many organizations struggle with transforming from the old style teams consisting of members with specialized silos of skills into Agile teams consisting of generalized specialists.  This results in sub-optimal Agile adoptions in Agile/Scrum environments, which is where most organizations transforming to Agile are advised to start.

    We will start with a look into the real role of QA in the organization, and where they truly add value in the production of quality code to allow the business to move forward. Piggybacking on the role of QA, we will then speak to exactly what QA needs to do to add value to the software development process, and how they integrate in the DevOps model that is a contemporary solution to an age old issue.  And, finally, we will speak to some uncomfortable truths, and draw conclusions into the skills that Agile Testers must be expected to master to allow the organization to pivot successfully into a truly Agile development group.

  • Liked Nitin Ramrakhyani
    keyboard_arrow_down

    Lean Roots to Grow, Wings to fly!

    Nitin Ramrakhyani
    Nitin Ramrakhyani
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    A lot has been said about Kanban and how these can be implemented in Software development, but the learning remains superficial till we go deep down to its roots to understand the core underlying practices and principles and why/how these practices evolved over a period of time. Infact the roots of most of the Agile methods can be traced back to Lean/Toyota Production Systems, a set of practices and techniques used by Toyota to build great set of cars with limited amount of resources. Even though building software is much different than building a car, there are many lessons and practices that can be learnt and applied nonetheless.

    In this interactive and visual talk, we'll take a virtual trip to Japan and learn some of the best practices/concepts that originated at Toyota for building "world-class" cars and see how each of these can be applied to software development. Learning about the roots of Lean should help the attendees in sowing the seeds of Lean improvement in their organizations and would help in building better software and improving the efficiency of the software delivery lifecycle.

  • 45 mins
    Workshop
    Beginner

    There is a level of "assumptions" that each one of us work with, while we deal with any system. Here in this case the system could be a team member, the manager, the management, or the entire organization. While we work with assumptions, the conversations or the discussions or the work we do, can seem like getting nowhere because of the conflicts, and a sense of frustration piles on .This is a common situation and a very common feeling amongst Coaches/Scrum masters/Project Managers or anyone dealing with project management scenarios. That is where "contracting" helps us get our way through!

    Contracting is a concept of "Transactional Analysis" school of psychology. Eric Berne defines it as "an explicit bilateral commitment to a well-defined course of action". Sometimes contracts will be multi-handed - all parties to the contract will have their own expectations. In the unusual event that these are all congruent, then fine. However, if not, then discussing everyone's expectations will lead to greater understanding and therefore to a clear contract. The risk in not doing this is that problems in completing the contract will emerge at some stage.

    3 Categories of contracts are administrative, professional and psychological.

    Administrative contracts deals with the operational agreements- like fees, who has to do what, time, frequency, attendees etc.

    Professional contracts deals with the expectations from each role and clarifies the essential setup required to achieve the same

    Psychological contracts talks about how we work as people and help to understand how we express our comforts/ discomforts       

    Amongst the three contracts psychological contracts are very essential and often ignored in projects. This type of contract will help us co-create any assignment and it’s a powerful tool for Agile coaches while they work with their teams, managers, organization etc.

    Further to agree with any contract, both the parties should operate from a space where there is mutual trust and concern (I am Ok , You are Ok).

    This report will discuss in detail about these contracts with examples from Agile projects, in an activity based sessions. We will also discuss the life positions based on 'I am OK, You are OK' theory.

    Note: Please note that this presentation is not about the business/financial contracts that most of us are aware of. However, the framework of contracts could be applied in any situation including the business/financial contracts.

  • Liked Arlo Belshee
    keyboard_arrow_down

    Agility: Step 1: Discipline; Step 2: Make Awesome

    Arlo Belshee
    Arlo Belshee
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    What comes after Agile? That depends on what you did for Agile. We will start by talking about the practices - and results - that only the top 2% of agile teams do. For most teams, this is what is beyond their Agile. Then we'll talk about patterns in the things that these top 2% are trying. Everything comes from the insane disciple Agile teams possess; let's look at how they capitalize on it.

  • Liked Vinod Purushothaman
    keyboard_arrow_down

    Hurdles: The sprint with impediments on the way to Automation

    Vinod Purushothaman
    Vinod Purushothaman
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Since the inception of Agile, practices has improvised and changed drastically. Continuous Integration and Continuous Delivery are few among them. I have practiced these methods and it really helped the team to deliver quality working software.

    Most of the team are working hard and trying to deliver on time. Automation leverages the team to make this happen through Continuous Integration and Continuous Delivery. We all know changes are really hard, and we have to surpass several challenges to succeed.

    We all are familiar with Sprints, here I am going to share the Hurdles I pass through to implement build and deployment automation. 

  • Liked Mukesh Bhangria
    keyboard_arrow_down

    Continuous Refactoring at Amazon: A Case Study

    Mukesh Bhangria
    Mukesh Bhangria
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Between the project deadlines, we always feel there is code which needs to be improved

    Usually Developers have the following 3 options:

    - Bite the bullet and do the refactoring as they go along.
    - Park the issue and address it later.
    - Allocate special time when the project gets out-of-control.

    As customer facing stories take higher priority, usually Developers are forced to choose the last option.

    However a team at Amazon took a different approach. Attend this session to listen to their first-hand story of how they changed this typical behavior to achieve Continuous Deployment on a critical service.

  • Joe Zachariah
    Joe Zachariah
    schedule 3 years ago
    Sold Out!
    20 mins
    Others
    Beginner

    Often times, as an organization matures into its Agile adoption space, many people begin to start looking at Agile as just another process, and forget that the one of the main tenets for Agile is 'People over Processes'. Ultimately we are all here to build exciting, quality assured, on time and within scope products and along the way also have some fun. But what if the team does not gel well together, to such an extent that it begins to affect the quality of the deliverables?

    That's the time when we need to look within our bucket of Agile best practices to understand which of those we can employ to even build a stronger team. Practices such as pair programming, continuous builds, retrospectives, etc. are all best practices which when employed at the right moment and at the right time, can help a team get together. 

    In this presentation, I am putting together a few songs from Bollywood movies, to describe in a fun way a team's transition through the four stages of team building - forming, storming, norming and performing. And how using some Agile best practices, the team could tide over the storming phase and move over to the performing phase. 

    This will be a 20 minute presentation, in which the first 5 minutes I will be talking, followed by about 15 minutes of a fun video which would be a mish mash of Bollywood songs highlighting all that my team went through in their Agile journey

  • Liked Naresh Jain
    keyboard_arrow_down

    SAMPLE PROPOSAL - Product Discovery Workshop

    Naresh Jain
    Naresh Jain
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Beginner

    Many product companies struggle with a big challenge: how to identify a Minimal Viable Product that will let them quickly validate their product hypothesis?

    Teams that share the product vision and agree on priorities for features are able to move faster and more effectively.

    During this workshop, we’ll take a hypothetical product and coach you on how to effectively come up with an evolutionary roadmap for your product.

    This 90 mins workshop teaches you how to collaborate on the vision of the product and create a Product Backlog, a User Story map and a pragmatic Release Plan.

    This is a sample proposal to demonstrate how your proposal can look on this submission system.

  • Liked Nitin Ramrakhyani
    keyboard_arrow_down

    Lean Roots to Grow, Wings to fly!

    Nitin Ramrakhyani
    Nitin Ramrakhyani
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    A lot has been said about Kanban and how these can be implemented in Software development, but the learning remains superficial till we go deep down to its roots to understand the core underlying practices and principles and why/how these practices evolved over a period of time. Infact the roots of most of the Agile methods can be traced back to Lean/Toyota Production Systems, a set of practices and techniques used by Toyota to build great set of cars with limited amount of resources. Even though building software is much different than building a car, there are many lessons and practices that can be learnt and applied nonetheless.

    In this interactive and visual talk, we'll take a virtual trip to Japan and learn some of the best practices/concepts that originated at Toyota for building "world-class" cars and see how each of these can be applied to software development. Learning about the roots of Lean should help the attendees in sowing the seeds of Lean improvement in their organizations and would help in building better software and improving the efficiency of the software delivery lifecycle.

  • Liked Ryan Martens
    keyboard_arrow_down

    Beyond Agile Execution: Agility for Business and Impact

    Ryan Martens
    Ryan Martens
    schedule 3 years ago
    Sold Out!
    60 mins
    Keynote
    Beginner

    Agile is not just a process change, its a mindset change for most. With faster time to market, better feedback and highly functioning teams, the Agile mindset opens our eyes to a better way of working as humans on large complicated and complex problems. Combining it with the concepts of Lean Startup, delivers another leap in team capacity and capabilities. It also opens the possibilities of using agility for more than just software development.

    Do you wonder how can we drive innovation in a disciplined way to tame our world's toughest problems? Can we apply the lessons learned from Agile and Lean Startup? Over the past three years, we've been able to apply agility at a new level, beyond business impact. Through our corporate social responsibility effort, "Rally for Impact", we aim to apply the agile mindset to mobilize citizen engineers to serve our communities and protect the planet. I want you to consider this growth path for yourself and your agile teams.

    Let's open the worlds mindset to a better way to empathize, explore and execute in these complex times.

  • 45 mins
    Workshop
    Beginner

    There is a level of "assumptions" that each one of us work with, while we deal with any system. Here in this case the system could be a team member, the manager, the management, or the entire organization. While we work with assumptions, the conversations or the discussions or the work we do, can seem like getting nowhere because of the conflicts, and a sense of frustration piles on .This is a common situation and a very common feeling amongst Coaches/Scrum masters/Project Managers or anyone dealing with project management scenarios. That is where "contracting" helps us get our way through!

    Contracting is a concept of "Transactional Analysis" school of psychology. Eric Berne defines it as "an explicit bilateral commitment to a well-defined course of action". Sometimes contracts will be multi-handed - all parties to the contract will have their own expectations. In the unusual event that these are all congruent, then fine. However, if not, then discussing everyone's expectations will lead to greater understanding and therefore to a clear contract. The risk in not doing this is that problems in completing the contract will emerge at some stage.

    3 Categories of contracts are administrative, professional and psychological.

    Administrative contracts deals with the operational agreements- like fees, who has to do what, time, frequency, attendees etc.

    Professional contracts deals with the expectations from each role and clarifies the essential setup required to achieve the same

    Psychological contracts talks about how we work as people and help to understand how we express our comforts/ discomforts       

    Amongst the three contracts psychological contracts are very essential and often ignored in projects. This type of contract will help us co-create any assignment and it’s a powerful tool for Agile coaches while they work with their teams, managers, organization etc.

    Further to agree with any contract, both the parties should operate from a space where there is mutual trust and concern (I am Ok , You are Ok).

    This report will discuss in detail about these contracts with examples from Agile projects, in an activity based sessions. We will also discuss the life positions based on 'I am OK, You are OK' theory.

    Note: Please note that this presentation is not about the business/financial contracts that most of us are aware of. However, the framework of contracts could be applied in any situation including the business/financial contracts.

  • Liked Sreerupa Sen
    keyboard_arrow_down

    Changing our Rhythm: Our Ongoing Journey towards Continuous Delivery

    Sreerupa Sen
    Sreerupa Sen
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Annual software release cycles cramping the agility of the team? Too many hot fixes reducing the efficiency of your organization? Customers waiting impatientlyfor  the next cool features hot off the press? These are some of the painful and common problems faced by development teams worldwide. In today's world, most things get outdated or out-of-fashion very fast - and software is no different. Users cannot afford to wait for the next cool set of features for a year. They want a steady stream of cool new features that they can adopt and use immediately.

    My team follows a development model that we like to call Open Commercial Development - where we're always connected to our stakeholders, our plans are out in the open, and we're always gathering feedback and reprioritizing. We used to have yearly releases of our product - a sort of big bang release with a host of new featres. Based on our stakeholder interactions, however, we figured that our software delivery wasn't agile enough for our customers. Users wanted new features incrementally throughout the year. They especially didn't want to wait a year for a feature that they'd requested that was critical for their business.

    So began our journey to Continuous Delivery - an interesting one for sure. It's not easy to deliver new features, manage technical debt, collaborate with users and incorporate their feedback into the new features - once every quarter. To do it consistently, with quality and on time, you need to have a framework in place - a combination of planning, process, automation and team organization - that lets teams focus on the right things to get to DONE DONE for their new features, and at the same time manage their quality and tecnical debt. Over the past year, we like to think that we've put that framework in place, and that is what I'd like to talk about in this session.

  • Liked Arlo Belshee
    keyboard_arrow_down

    Agility: Step 1: Discipline; Step 2: Make Awesome

    Arlo Belshee
    Arlo Belshee
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    What comes after Agile? That depends on what you did for Agile. We will start by talking about the practices - and results - that only the top 2% of agile teams do. For most teams, this is what is beyond their Agile. Then we'll talk about patterns in the things that these top 2% are trying. Everything comes from the insane disciple Agile teams possess; let's look at how they capitalize on it.

  • Liked Vinay Krishna
    keyboard_arrow_down

    Effective 9 Practices to minimize technical debt

    Vinay Krishna
    Vinay Krishna
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Often we find it difficult to incorporate any changes in a software project during later phases of its development, or during post-delivery maintenance. Primary reason for this is inflexibility in design and code which makes it difficult for changes to be incorporated. This inflexibility substantially increases the cost of making changes and this metaphor has been termed as Technical Debt.
    While Technical Debt cannot be eliminated completely, its burden needs to be reduced. Many agile practitioners have suggested some practices to avoid or eliminate Technical Debt.
    In this session I shall discuss about a method to get relief from Technical Debt and talks about nine proven practices that a developer can follow to minimize Technical Debt. These practices help to:

    • Change the coder's mindset so that they should use technical practices i.e. various refactoring techniques to reduce technical debt in code and design
    • Developers to plan and manage the time to pay down the debt i.e. determine your living budget
    • Take minimal technical credit in design and code

    These practices have been used and found to be effective when implemented in projects which will be used as a case study.

  • Liked Ankush Sabharwal
    keyboard_arrow_down

    Getting Familiar with Agile & Scrum, including sizing in Agile

    Ankush Sabharwal
    Ankush Sabharwal
    schedule 3 years ago
    Sold Out!
    90 mins
    Talk
    Beginner

     

    This session is on Fundamental and Practical overview of Agile, focusing on Scrum and XP practices. Creating good User Stories and sizing them will also be explained in the session along with the details about some of the metrics used in Agile.

  • Liked Prashant Kutade
    keyboard_arrow_down

    How should be a Sprint Retrospective ?

    Prashant Kutade
    Prashant Kutade
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Beginner

    Sprint Retrospective

    Sprint Retrospective is a meeting that happens at the end of each Sprint that usually occurs after the Sprint Review. This practice involves the Scrum Master and the team members to discuss what went right and what went wrong in the practices adopted during the Sprint. Thus, it allows modify some practices to maximize the positive and avoid negative points. This meeting provides a moment for greater interaction among the members and allows the team to self evaluate and propose the necessary changes, thereby strengthening the sense of teamwork.

    Like the other meetings in Agile, the Sprint Retrospective requires many adjustments. In the experience reported in one of the Sprint Retrospective in John Deere TCI(Pune, 2013), someproblems that were faced related with the presence of all members at the meeting and related with the tool support. The first trouble was to find a time when everyone could attend, since this meeting was initially scheduled one day after the Sprint Review. The solution was to hold the meeting after the Sprint Review and limit the maximum duration for two hours, so this is not tiring. The second difficulty is the need for multiple tools for holding the meeting, the techniques to be followed to drive the meeting and raise the positive and negative suggestions, as well as project management tool like Rally for presenting data from the project’s progress, such as the Product Burndown.

    Despite the importance of the presence of all team members in the Scrum meetings, in some situations, for example, a project with many distributed teams, a remote meeting with all members becomes impractical which should be avoided. Thus, for those situations, this proposed approach suggested to do a Sprint Retrospective by team, and saving the information collected at each meeting. This information collected should be shared to all members, allowing them to analyze the improvements suggested by other teams.

    One last modification is to hold a meeting among each Scrum Master, similar with Scrum of Scrums, to discuss the Sprint Retrospective done by each team, and with that, it is possible to align the dependency among them. This meeting may occur the day after the Sprint Retrospective of the teams, and it is crucial that each Scrum Master considers the points raised by other teams before the meeting between them, in order to optimize its duration.

  • Nasser Hadjloo
    Nasser Hadjloo
    schedule 3 years ago
    Sold Out!
    20 mins
    Case Study
    Beginner

    In the global village, some talks inEnglish the others in their own local langauge, when it comes to the global websites with international users, their users should be able to interact with the website with their own language.

    The process of internationalization for a large-scale application (website) is usually time consuming; I'll show you how to split the internationalization process into different sprints and implement a successful internationalized application.

     

  • Liked Karthik V
    keyboard_arrow_down

    Revving up Scrum with Blitz – Collaborative workshop to organize the Epic backlog

    Karthik V
    Karthik V
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Beginner

    Most features have a lead time before Requirements, Architecture and Epic Backlog is available to the scrum team. There is a misconception that these Sprint zero, or planning Sprints are the way of Scrum but are actually waterfall methods. Also this approach doesn’t essentially lead to team empowerment of the product backlog during sprint execution.

    Blitz – brings in a time boxed intense collaborative approach with involved stakeholders and scrum team agreeing on requirements, architecture, acceptance criteria and product backlog priorities. This is part of the Scrum execution cycle rather than a Sprint 0/Planning exercise.This brings in a parallel and lean approach to expedite a refined development ready product backlog.

    This is an approach executed at various projects to reduce the feature delivery timeline and understand/minimize the unknowns.

  • Liked Karthik Kamal Balasubramaniam
    keyboard_arrow_down

    7 Deadly Sins of 'Agile- But' Teams

    Karthik Kamal Balasubramaniam
    Karthik Kamal Balasubramaniam
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    This report is based on the analysis of the epidemic called ‘Agile-But-Teams’ in services organization. The presentation would cover the following 7 anti-patterns in such teams,

     #1 Fix ‘everything’ in your contract (definitely no breathing space) 

    Sign contracts with fixed scope and penalties. Ensure you include at least 30 metrics with fixed targets without accounting for team’s capability.

      #2 Don’t groom your requirements, make them look beardy and scruffy 

     Ensure your product backlog grooming is either not taken seriously or not done until the first day of the sprint.

     #3 Be a salary thief and never change a thing 

    Freeze your process steps in the beginning of the project and create checklists that would ensure compliance on a monthly basis. If possible, include mechanisms for tailoring and deviation, but never change the process.

     #4 Be loyal to the law of averages 

    Set organizational baselines for Agile teams and measure them periodically. Also, get RCA’s and reasons for missing the organisation targets.

     #5 Trust the pyramid and mummies 

    Adhere to the team pyramid structure and give the product responsibility to the identified leads.

     #6 Never Tell, Only Ask 

    Never change your product development/testing practices empirically instead implement industry ‘best’ practices based on case studies from other projects.

     #7 Make Self-fulfilling prophecies 

    Constantly discuss about, how Agile is not the right model for your project. Ensure your prophecies are fulfilled and there is no redemption whatsoever

     The presentation would also cover the possible antidotes for the scenarios and explain in detail about the behavioral sciences behind such patterns.

  • Liked Meghana
    keyboard_arrow_down

    TFS based Workitems tracking (WIT)

    Meghana
    Meghana
    schedule 3 years ago
    Sold Out!
    20 mins
    Workshop
    Beginner
    TFS is used as an integration environment for feature and task planning, issue and defect tracking. Tool mix (MSProject, local-in-house tools) and MSExcel “hell” is therefore obselete.
  • Liked Meghana
    keyboard_arrow_down

    Poka-Yoke: Error-Proofing SW the LEAN way

    Meghana
    Meghana
    schedule 3 years ago
    Sold Out!
    20 mins
    Tutorial
    Beginner
    In the words of Mary Poppendieck; inspection to find defects is a waste, inspection to prevent defects is essential. This session aims to provide an insight into developing SW based Poka-Yoke
  • Liked Karthik Kamal Balasubramaniam
    keyboard_arrow_down

    Anatomy of a Self Organizing Team

    Karthik Kamal Balasubramaniam
    Karthik Kamal Balasubramaniam
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    What does it mean by a ‘Self-Organizing team’?  Or it’s just an euphemism for something else? Or even worse-it’s just a fancy term?

    This particular entry is a result of my relentless pursuit in search of a ‘Self Organizing’ team. I have always doubted the existence of such mythical teams, however my perseverance made me search for them whatsoever. In this short presentation, I would like to present the experience of my journey and observations on the anatomy of such teams. However reluctant I was, I decided to add some data points to my personal journey to make it more sellable. Fortunately, few of the observations are not very different from the accepted reference points. Hence I would also refer to the group behaviors explained by various psychologists like Sigmund Freud, Eric Berne etc in this short talk.

  • Liked Pramod Sadalage
    keyboard_arrow_down

    Ten Patterns of Database Refactoring

    Pramod Sadalage
    Pramod Sadalage
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Over the life of an application as requirements change, application usage patterns alter, load and performance changes the need to change database and database architecture is inevitable. There are patterns of these changes such as

    1. 1. Encapsulate Table with View
    2. 2. Migrate method from database
    3. 3. Replace method with views
    4. 4. Introduce Read only table
    5. 5. Split table
    6. 6. Make column non-nullable
    7. 7. Drop column
    8. 8. Add foreign key constaint
    9. 9. Merge columns
    10. 10. Replace columns

    In this talk we will discuss the above database refactoring patterns and different implementation techniques to enable blue, green deployments, allow for legacy applications to work with fast changing database and enable the teams to effectively refactor the database to fulfill the changing needs of the organization.

  • Liked Gerry Kirk
    keyboard_arrow_down

    Create an Agile virus in your organization, empower your team, change your life

    Gerry Kirk
    Gerry Kirk
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Beginner

    Need buy in from a key manager or executive to adopt Agile? Desiring better team collaboration? Hungry for a saner life at home?
    Try Personal Kanbanwinner of the Shingo prize for Operational Excellence. It's the fastest, simplest way to taste test the goodness of the Lean Agile approach to managing knowledge work. Personal Kanban empowers small teams and individuals, at work and at home.Give that overwhelmed executive instant relief. Build your own system, and soon curious onlookers ask and then create their own. Look out, you've just released an Agile virus in your organization!
    You've also discovered a way for you and your team to get more out of your efforts, to improve communication, and find time for the things that matter most.In this session you'll learn how to create a Personal Kanban system through stories, examples and interactive exercises. Walk away understanding the psychology behind visualizing work and limiting work in progress, inspired and motivated to make a difference at work and home. 

  • Liked Johannes Brodwall
    keyboard_arrow_down

    Practice agile programming with coding dojo

    Johannes Brodwall
    Johannes Brodwall
    Buddhima w.wickramasinghe.
    Buddhima w.wickramasinghe.
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    A Coding Dojo is a fun and social way to become a better programmer. Johannes is an experienced coding coach who will guide you through a few hours of programming that will transform your understand your craft and yourself as a programmer. In the workshop you get to try out pair programming, test-driven development and continuous refactoring for yourself and you get lots of recommendations on how to improve your coding and testing. You will need to bring your own computer with a development environment of your choice. Recommended for Java, Ruby, JavaScript and C# developers.

    This is what previous participants say about the workshop:

    • What did you learn? New tools, pair programming and fun exercises; Ide tricks, programming language basics, testing tools, using tests as a reasoning tool; you can comfortably pair with strangers.
    • What surprised you? Small steps work better than planning; It's easy to get started when you pair program; Pair programming is nice
    • What do you plan to do next? Using TDD every day; Listen to partner more carefully - he may already have solved the problem.
  • Liked Priyank
    keyboard_arrow_down

    Deriving business case for a Product development ( using Agile Innovation Game )

    Priyank
    Priyank
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    In this session participants will learn how to 'derive a business case for a product' using simple method aka AGILE GAME (also known as Innovation Games, Gamestorming )

    Agile innovation games are one of the most effective way to solve a business problem or derive a solution. (For detail refer: www.innovationgames.com)  Participants will play Hot Air Balloon game to 'derive a business case for a product'. This game can help  -

    • Derive a Business Case
    • Identify Constraints & the path to solution.
    • Get multiple stakeholders on the same page
    • Identify RAIDS upfront
    • Plan to mitigate risk early in the cycle
  • Liked Ellen Grove
    keyboard_arrow_down

    Build Your Dreams: User Requirements Gathering with LEGO Serious Play

    Ellen Grove
    Ellen Grove
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    Let your hands be the search engine for your brain! LEGO® Serious Play® is a powerful thinking, communicating and problem solving technique that can help you and your team do serious work through structured play activities using a popular and playful 3D modeling toy. Through a facilitated process of building models that, storytelling and reflection, every person at the table is engaged and actively participating in the discussion, whether the topic is individual aspirations, team relationships, developing a new product or solving a wicked organizational problem. Everyone builds and everyone tells their story – all participants have equal opportunity to put their own points of view on the table, unlocking new perspectives and exposing the answers that are already in the room.  LEGO Serious Play has been used successfully for team-building and problem solving in a variety of organizations, from NASA to RBC to academic settings and public utilities.  

    This presentation provides a hands-on introduction to LEGO Serious Play, so that you can experience firsthand how using LEGO to do real work unleashes creativity and enables meaningful conversations in a very short time. We will explore how to use this playful technique to collaboratively elicit information about user requirements and strategic design issues using the open source User Requirements with Lego methodology developed by a team at the University of Lugano, Switzerland.  This approach is particularly suited to Agile teams that want to get team members and stakeholders sharing their different perspectives on common goals in an open and light-weight manner.

  • Liked Tathagat Varma
    keyboard_arrow_down

    Designing agile feedbacks for agile learning - an experience report

    Tathagat Varma
    Tathagat Varma
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Feedback is perhaps the most important aspect of the overall agile lifecycle. If the feedback is too wide and shallow, it won't give enough actionable feedback. If it is too narrow and deep, it might fail to register feedback outside its focus area. So, how does one go about designing feedbacks that enable agile learning. We call them agile feedbacks.

    In this brief session, we will share an experience from designing agile feedbacks for agile trainings and workshops. The objective was to get most critical feedback in shortest amount of time to enable quick action planning. We created feedback that took a maximum of 5 minutes and enabled the most important learning in both, focussed as well as open-ended manner that allowed us to focus on the most critical items. We employed elements of Design Thinking and Rapid Iterative Testing and Evaluation (RITE) to improve the process and quality of feedback themselves. We will also be touching up these concepts and how effective they were.

  • Liked Richard Kasperowski
    keyboard_arrow_down

    Self-management and Self-organization: Agile Games with Motion

    Richard Kasperowski
    Richard Kasperowski
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    Self-management and self-organization are important themes in Agile software development, but what do they actually look like?  We pontificate about worker empowerment, but then we revert to command-and-control: our product owners mandate project scope and deadlines, and our Scrum Masters assign tasks to team members.  Why can’t we let teams be self-organized and workers be self-managed?
     
    These activity-based learning activities are kinesthetic learning games.  Players learn by playing fun, physical games of movement.  These games create a social atmosphere and a full body and mind experience that make it easy and fun to learn.  We’ll play five games, including Line Up, 60 Paces, Triangles, Human Knot, and a special surprise game.
     
    In this session, we explore and experience self-management and self-organization via Agile games.  You will leave with a deep internalized understanding of self-management and self-organization and an appreciation of how they work better than command-and-control.  You’ll be able to share these games with your coworkers.

  • Liked Howard Deiner
    keyboard_arrow_down

    Pivoting Your Organization to Become Agile Testers

    Howard Deiner
    Howard Deiner
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Many organizations struggle with transforming from the old style teams consisting of members with specialized silos of skills into Agile teams consisting of generalized specialists.  This results in sub-optimal Agile adoptions in Agile/Scrum environments, which is where most organizations transforming to Agile are advised to start.

    We will start with a look into the real role of QA in the organization, and where they truly add value in the production of quality code to allow the business to move forward. Piggybacking on the role of QA, we will then speak to exactly what QA needs to do to add value to the software development process, and how they integrate in the DevOps model that is a contemporary solution to an age old issue.  And, finally, we will speak to some uncomfortable truths, and draw conclusions into the skills that Agile Testers must be expected to master to allow the organization to pivot successfully into a truly Agile development group.

  • Liked Tamizhvendan S
    keyboard_arrow_down

    Intellisense for your intimidating data

    Tamizhvendan S
    Tamizhvendan S
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Beginner
    A growing trend in both the theory and practice of programming is the interaction between programming and rich information spaces. From databases to web services to the semantic web to cloud-based data, the need to integrate programming with heterogeneous, connected, richly structured, streaming and evolving information sources is ever-increasing.
     
    No matter what technology we use for accessing data, someone, somewhere needs to somehow specify how to map data from the source to a structure that can be used in the programming language.
     
    With F# 3.0 you now have a tool that massively simplifies information-rich analytical programming. F# 3.0 provides integrated support for F# Information Rich Programming, a new and powerful way of integrating data and services into your programming experience.
     
    This talk would demonstrate what F# 3.0 specifically offers in the area of Information Rich Programming (IRP), but also look at how information-richness makes us reconsider programming language and tooling design more generally, and take a look at the themes that recur in this kind of work.
  • Liked Abhilash Chandran
    keyboard_arrow_down

    Workshop- Agile user story and Behavior Driven Development (BDD) using Gherkin

    Abhilash Chandran
    Abhilash Chandran
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    In this session I will introduce the audience to the concepts of Gherkin language. Gherkin is a popular language used to encapsulate the requirements in agile world.

    This was successfully implemented in our group across India & USA. I will go through this case study also.

     

  • Liked Pradeepa Narayanaswamy
    keyboard_arrow_down

    WORKSHOP- Defining Behaviors as a team

    Pradeepa Narayanaswamy
    Pradeepa Narayanaswamy
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    In lot of agile teams, often times, all the team members will be doing the grooming and planning exercise as a team. Often times, defining the behaviors is either ignored, overlooked, skimped or done by individuals on their own without a common understanding as a team.

    To solve this problem, I have used this hands-on time-boxed activity for all of my teams to define behaviors as they move along in the sprint. This will help all the team members to have a shared understanding on their users and their behaviors as it relates to their user story. This is an activity that any agile team member can take and implement the next day at work.

     

     

  • Liked Pradeepa Narayanaswamy
    keyboard_arrow_down

    Agile Testing- What is my success mantra??

    Pradeepa Narayanaswamy
    Pradeepa Narayanaswamy
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    As more and more organizations are transitioning to agile, it’s inevitable that Agile testing is not just a concept any more. It is also not just about placing a tester in every team. What is so radically different now? How to be successful at agile testing? How to be an effective cross-functional team that embeds and honors all specialties including testing?

    In this presentation, I am going to share my teams’ success with Agile testing and how we incorporated these 3 aspects – people, process and tools/techniques. This talk will benefit any members in an organization who has a stake in the product quality. It is also highly beneficial for those agile testers (from aspiring to veteran) to understand the 3 main aspects as it relates to testing and why we need to embrace- not just one, not two, but all these 3 aspects to be successful in Agile testing. 

     

     

  • Liked Tarang Baxi
    keyboard_arrow_down

    1000 Words - Illustrating Project Challenges with Visuals

    Tarang Baxi
    Tarang Baxi
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    A project can face varied challenges through its life, foreseen and otherwise - runaway scope, high defect volumes, depressed velocity, and many more. Addressing many of these first requires recognition of the problem and then action from one or more sets of project stakeholders. Telling the story with simple visuals can be a very powerful way to articulate a challenge (the what), the potential root causes (the why) and the options available to fix it (the now-what). Teams typically already track a lot of data related to throughput, quality, scope and cost. Creative use of this data combined with simple, hand-crafted visuals can be much more effective than hundreds of bullet points. In this hands-on workshop, you get to exercise your visual thinking and visual communication skills. We introduce some simple visual thinking techniques like Look-See-Imagine-Show, and then let you apply them in a project simulation, so that you can practice hand-rolling simple visuals that speak volumes (no fancy tools needed!).

  • Liked Vinod Purushothaman
    keyboard_arrow_down

    Hurdles: The sprint with impediments on the way to Automation

    Vinod Purushothaman
    Vinod Purushothaman
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Since the inception of Agile, practices has improvised and changed drastically. Continuous Integration and Continuous Delivery are few among them. I have practiced these methods and it really helped the team to deliver quality working software.

    Most of the team are working hard and trying to deliver on time. Automation leverages the team to make this happen through Continuous Integration and Continuous Delivery. We all know changes are really hard, and we have to surpass several challenges to succeed.

    We all are familiar with Sprints, here I am going to share the Hurdles I pass through to implement build and deployment automation. 

  • Liked Janardhanam Venkat
    keyboard_arrow_down

    DevOps - In an Enterprise from Cradle to Grave

    Janardhanam Venkat
    Janardhanam Venkat
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Beginner

    Commercial software development teams that practice Agile are confronted with daunting challenges in optimizing operations. In particular, the primary challenges faced are in shorter development sprint and bottle neck at QA gates for operations. The session will provide insight of DevOps building block and its business benefit. The session demonstrates signs that you need DevOps. This session is focused on how CollabNet’s engineering and operations team is overcoming these challenges and thus delivering faster and with a much better fit to enterprise customer requirements. The session touches upon the ops involvement from the beginning of the release till go live of the product development and briefly cover few real world examples.

    CollabNet is a leading innovator in software development tools and in agile practices. Its Chennai development facility collaborates with teams in the USA, South America and Europe on large, production-grade software development projects. Venkat will provide a real-life case study of how CollabNet leverages a unified collaborative infrastructure to drive practices like continuous integration and DevOps to meet customer requirements.

  • Liked Abhilash Chandran
    keyboard_arrow_down

    Agile Appraisal: Sprint Iterations for Appraisal reviews

    Abhilash Chandran
    Abhilash Chandran
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Beginner

    Appraisal reviews are always hard. Traditionally it is done once a year. The manager and employee undergo a tough period of reviews, discussions and ratings. At the end no one is happy.

    • Manager
      • Manager is forced to provide a feedback of an entire year in few minutes.  
      • Because of time constraints and lack of useful data, a constrictive feedback is not given.
      • In most of cases this ceremony is reduced to mere salary negotiations.
    • Employee
      • Employee feels cheated because of lack of any concrete feedback
      • Employee is not able to proactively discuss his/her career objectives and create a proper plan to bridge the talent gap.

    In this talk I will discuss some of the approach we are trying to follow in our group to align appraisal feedback also along with agile sprints.  

    I will present the experience report of how we are converting the age old waterfall appraisal process to Agile. I will discuss the need for this change, the general idea and the challenges we are facing.

    In this new way of appraisal management the focus is on the individual. Just like we have a Scrum/Kanban board, each employee will have a talent and improvement board. Instead of developing a product, the focus is to develop an individual. Like the scrum there are Ceremonies

    • Release planning – Organizational agenda
      • Decide Group & team goals
    • Sprint planning
      • Work with each team members to identify some “traits”/action points to improve
    • Review
      • Review the outcome
    • Retrospective
      • Based on the outcome revisit the individual goal & do a re-planning
  • Prajakta Thakur
    Prajakta Thakur
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

     Prioritization, Accountability, Inspect-and-adapt, Rhythm, Feedback, Collaboration, Self-Organization, Focus form the key principles of Scrum Methodology. And it is the Scrum Ceremonies which help ensure that this essence of Scrum remains intact through following of the above principles. Scrum Ceremonies give project teams a wholistic framework to ensure smooth Scrum implementation and effective project delivery.

    The key Scrum Ceremonies are as listed below

    • Release Planning & Sprint Planning ( consisting of Backlog creations and grooming and Estimation )
    • Daily Scrum
    • Sprint Review
    • Sprint Retrospective

    The scope of this presentation is to share:

    • Deeper understanding of objectives behind each ceremony
    • Benefits of each ceremony
    • Challenges and Common Mistakes related to each ceremony
    • Effective techniques of conducting the ceremony to get best advantage out of it
  • Prajakta Thakur
    Prajakta Thakur
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Beginner

     

    Scrum Team’s success depends totally on how the Product Owner, the Scrum Master and the Scrum Team perform their responsibilities well.

    Product Owner’s is a multi-faceted role. A PO undertakes a range of responsibilities like maintaining product backlog; prioritizing items as per business value or return on investment; conveying vision and goals to the team, engaging customer, participating in scrum ceremonies, monitoring product progress, liaising with team for effective delivery and so on.

    Scrum Master has the onus to protect the team from outside interference, help the team resolve impediments , guide the team and PO to effectively adopt Scrum Processes, monitor the project without command and control

    Whereas a cross functional Scrum Team of Developers, Designers, Architects, Testers,etc. have to undertake functions like Analysis, Estimation, Design, Development, Testing, Deployment in an effective manner. They have to self-manage and self-organize to achieve committed deliverables and hold accountability for the success of each iteration

    Type of product, product lifecycle stage, project size, domain knowledge of the team are various factors which further govern what all responsibilities a Scrum Team needs to shoulder. With such huge gamut of responsibilities to be managed, it is bound that a Scrum Team commits mistakes.

    This session attempts to showcase some of the common mistakes, which Scrum Teams commit and ways to avoid these mistakes. Awareness of these common mistakes or lessons learnt will help teams to prevent such scenarios and ensure effective delivery.

  • Niraj Bhandari
    Niraj Bhandari
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    This talk is my self-reflection as a Product Owner (PO) over the last year and a half. Coming from a technical background where techies “don’t talk much” and “work with their headphones on”, I too was more of a good listener into discussions and spoke only on select occasions. We are always taught to listen first and ask only if you are not clear. Especially in Indian context, asking questions are not encouraged much, and even in colleges profs are happy if you don’t engage them in discussions. And on top of it, if you belong to the tribe of introverts like me then you have had it. A combination of these factors ensured that, I too spoke little and only when needed and banked heavily on my work to do the talking.

    If it seems like a familiar script, either of yourself or of somebody you know then I recommend that you attend the session.

    This talk is centered on my learning and the move from a silent PO to an assertive PO, the challenges and the opportunities. The role of a PO is very delicate one and the person needs to have a very balanced approach. He/She can’t be a silent observer, and at the same time he/she can’t be an aggressive participant. “Silence is Golden” doesn’t applies to POs and the tribe needs to maintain the balanced communication channels while engaging all the stakeholders for the success of the project and that is what we will be focusing on in this session.

  • Liked Hameet
    keyboard_arrow_down

    Different Ways to Product Backlog Grooming

    Hameet
    Hameet
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

     

    Product backlog contains list of desired functionalities of an envisioned end product. It provides the bigger picture than the sprint/iteration backlog. If product backlog is neglected and treated as a dumping ground, it can distort the bigger picture and impact the iteration/sprint planning. In essence, a well-groomed product backlog is a prerequisite for a successful sprint planning meeting. As part of product backlog grooming exercise:

    - New items are discovered and described.

    - Existing items are changed or removed as appropriate.

    - Items are prioritized. The most important items being at the top.

    - High-priority items are decomposed and refined for upcoming sprint planning meeting. 

     

    But this poses few questions:

    - How much time should be spent in product backlog grooming?

    - How frequently product backlog grooming should happen?

    - What are different ways to product backlog grooming?

    - How product backlog grooming exercise can be made efficient over time?

     

    In this session, we will touch base on 

    - the factors resulting in growing product backlog

    - the indicators of unhealthy product backlog

    - the impact of unhealthy product backlog on the product development

    - the various approaches to take control of the product backlog 

    - the tips for maintaing a healthy product backlog