• 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 Cara Turner
    keyboard_arrow_down

    Building Creative Teams: Motivation, Engagement and Retrospectives

    Cara Turner
    Cara Turner
    schedule 3 years ago
    Sold Out!
    90 mins
    Talk
    Advanced

    How do software teams become creative? If you're not a start-up, does creativity even play a role in the business driven world of software development? Idea generation is the basis of all our work - no matter how challenging or mundane. With a scientific approach to implementing change, creativity is the basic tool we have for addressing the challenges of software development.

    This talk explores the elements of engagement and creativity along with the neuroscience of generating ideas. These give us specific insight into how employing different agile retrospective formats over the course of the product development process can extend our usual practices and develop a thinking mind-set comfortable with tackling daily work with a fresh and explorative approach.

  • Liked Michael Heydt
    keyboard_arrow_down

    Applying Lean UX to Capital Markets - Lessons From a Year of Lean UX on Wall Street

    Michael Heydt
    Michael Heydt
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The Lean UX approach to interaction design is a spectacular model for defining and implemented what is needed in appications to support the users in their jobs, as compared to technical deliverables that in the end often do not meet the needs of the users.  In this talk, I will go over strategies for applying lean UX practices to capital markets projects, adapting UX to agile processes, including executing user interviews, rapid UX design, mockups to UI prototypes, and rapid implementation through continuous delivery and end user experience / acceptance testing.

  • 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 Todd Little
    keyboard_arrow_down

    Mythbusting Software Estimation

    Todd Little
    Todd Little
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Estimating software projects has proven to be particularly challenging. Over-running schedules happens frequently in our industry. Todd will look into some of the reasons for these challenges by exploring a number of myths of software estimation and then setting out to validate or bust these myths.

  • Liked Jez Humble
    keyboard_arrow_down

    Why The Project Paradigm Kills Innovation, and What To Do Instead

    Jez Humble
    Jez Humble
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Projects were invented as a vehicle for managing civil engineering projects. But software has completely different characteristics from, say, a bridge. In this talk I'll explain why the use of projects causes significant dysfunction, and how to build innovative products and services at scale based on lean principles.

  • 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.

  • 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 Todd Little
    keyboard_arrow_down

    Mythbusting Software Estimation

    Todd Little
    Todd Little
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Estimating software projects has proven to be particularly challenging. Over-running schedules happens frequently in our industry. Todd will look into some of the reasons for these challenges by exploring a number of myths of software estimation and then setting out to validate or bust these myths.

  • Liked Jez Humble
    keyboard_arrow_down

    Why The Project Paradigm Kills Innovation, and What To Do Instead

    Jez Humble
    Jez Humble
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Projects were invented as a vehicle for managing civil engineering projects. But software has completely different characteristics from, say, a bridge. In this talk I'll explain why the use of projects causes significant dysfunction, and how to build innovative products and services at scale based on lean principles.

  • 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 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 Karthik Sirasanagandla
    keyboard_arrow_down

    When Agile becomes Fr-agile..learn your lessons the fun way!

    Karthik Sirasanagandla
    Karthik Sirasanagandla
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate
    So you have heard of "Code Smells". Did you hear of "Agile Smells"? Yes or No; then this session is for you (us).
     
    In this session, Karthik intends to talk about the very many things that go wrong in companies that attempt to be or become Agile.
    But fault-finding is the easiest thing. Can Karthik provide concrete solutions? Yepp, he intends to share the solutions as well for most if not all the problems.
    And in same breadth seeks to know what others has to offer from their experience.
     
    Piquing your interest? Are you wanting to get a taste of some of the Agile smells? Below are some of them:
    * Belated Stand-ups
    * Non-participative stand-ups
    * War-zone Retrospectives 
    * Unfruitful Sprint planning meeting
    * Zero-Test development
    * Inverted Test Pyramid development
    * Gate-keeper QAs
    * Hierarchical Roles
    * Velocity Driven Development
     
  • 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.

  • Niranjan N V
    Niranjan N V
    schedule 3 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    Usage of Agile methodologies such as Scrum, Scrum-XP, FDD, Crystal and methodologies has become increasingly large in IT Industry and also non IT industries. As the usage of agile methods becoming wide spread, the effectiveness of implementation of these agile practices in projects, organizations become more important for success of agile. Agile manifesto and 12 agile principles, acts as guiding principles and helps in the agile deployment. But when it comes to operational daily tasks, there is no method to ensure whether agile projects implement 4 values of manifesto. For traditional methods of software development we have standards such as CMMI,ISO etc. This paper makes an attempt to defining Maturity Model for agile projects.

    Following maturity model has been defined after our experience in consulting and training agile methods.

    Level

    Categorized by

    Guidelines for Description

    Maturity Rating based on Focus Areas

    1

    Basic

    1) Following traditional Water fall approach for delivery. 2) Agile practices used in pockets. 3) Requirements/Features (Product backlog items) are more at high-level or Epics levels

    Any Focus area <= 50%. Overall Compliance <=50%

    2

    Managed

    1) Product backlog items are broken from EPICs   into development user stories, product back log grooming is done 2) Basic metrics used and not very strong in prediction of the current performance, timeliness of deliverables 3) The Agile team delivers business value occasionally

    All Focus Areas - 50% and 75%. Over-all compliance- 50-75%

    3

    Matured

    1) Iteration Status , Agile Metrics in place using Agile Tasks Board 2) Usage of historic data such as velocity, story points committed v/s delivered for forecasting and estimation 3) Team reports the Iteration Effectiveness, Release Effectiveness to different levels of management like functional manager, Product Owner and Top management. 4) Team is skillfully using the Agile Engineering Practices in projects if not at Program Levels

    All Focus Areas - >75% Overall compliance > 75%

    To validate the maturity levels defined, an assessment of agile practices in projects are done and mapped into following focus areas.

     

    Focus Areas

    Development Practices/ Infrastructure

    Iteration Planning/ Tracking

    Product Ownership

    Release Planning/ Tracking

    Team Cohesiveness( Collaboration)

    Agile Testing Practices

     

    In order to rate the maturity levels for any project, the compliance of agile practices are mapped into above focus areas and Radar Chart is plotted to depict the compliance of each of these focus areas and are the agile mturity in projects.

     

     

     

     

  • Dipesh Pala
    Dipesh Pala
    schedule 3 years ago
    Sold Out!
    90 mins
    Talk
    Intermediate

    Breaking up User Stories can sometimes be as painful as a relationship break up - but it does not have to be like that!

    Our experience has shown us that the key to getting full benefit from introducing Agile is in how the project work is broken up. When it gets difficult to see how to write small enough user stories, teams often resort to technical story cards. While this can give the team visibility of the work that is being done, the business is not seeing potentially implementable product, or early delivery of business value.

    This talk will dig a lot deeper to expose the real reasons for splitting up user stories and not just talk about doing it as a good practice - we must BE Agile not just DO Agile!

    Using real-world examples, this talk will also offer a set of guidelines and some unconventional ways for breaking up larger chunks of work into valuable user stories that can help Agile teams become more successful.

  • 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 Abrachan Pudusserry
    keyboard_arrow_down

    Manager and Photographer

  • Liked Maris  Prabhakaran
    keyboard_arrow_down

    Coaching Mantras for Agile Team

    Maris  Prabhakaran
    Maris Prabhakaran
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    15 valuable Mantras which will crate value for Agile Team .

    These mantras are implemented and created value for the Agile Team

    Mantras for Product Owner

    Mantras for ScrumMaster

    Mantras for Agile Team

    Mantras for Agile Coach

    Learn Global Mantras from the session.

     

     

     

     

     

    10

  • 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 Binoy Shah
    keyboard_arrow_down

    Path for Effective Project Planning in AGILE

    Binoy Shah
    Binoy Shah
    schedule 3 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    Agile development has slowly and steadily made its way into the
    software industry. With increasing competitive pressure, Agile
    development helps an organization to churn out working software
    faster, thus adapting to changing business demands and generate a
    competitive advantage. There are however a few misconceptions
    about Agile software development. One of them is that there is
    little or no planning done in Agile. In this paper, we aim to dispel
    this myth.
    Planning a software implementation project in Agile, is similar to
    planning a project in any other software development
    methodology, however it is fundamentally different. As opposed
    to extensive, up-front planning required in other methodologies,
    agile planning simply follows an incremental approach to
    planning, just like agile development. This requires an initial
    planning to be done during earlier stages of the project and
    iteratively revisit the plan as we make progress and gain more
    insights during implementation.
    Agile Planning though incremental, strongly follows the
    principles of the “Iron Triangle of Project Management”. The
    triangle of project management is structured around the three
    vertices of Scope, Cost and Time. In this paper, we have
    attempted to break the entire agile planning process in 7 steps.
    Also we have depicted how each of this vertex is defined in its
    respective phase. We have also discussed some best practices to
    define each vertex of the Triangle and how the three vertices are
    connected to create the Iron Triangle, which is termed as Release
    Planning in the Agile world.

  • Dipesh Pala
    Dipesh Pala
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Once upon a time, Martians and Venusians met, had happy relationships together and accepted their differences to work towards delivering a project. Then came Agile and amnesia set in! ScrumMasters and Product Owners forgot they were from different planets. All of a sudden, Product Owners, ScrumMasters and the team members found themselves sitting around a table discussing user stories and potential solutions.

    This unprecedented access and communication created a whole new set of challenges… Sometimes it feels like our team members are from different planets, as if one is from Mars and the other is from Venus. You may have heard of Mars and Venus in the bedroom but this presentation will be talking about Mars and Venus in the team room.

    Based on my many years of experience in coaching and working with people in these roles, this presentation will describe why and how ScrumMasters and Product Owners react differently to various situations in a team room. The key is in understanding how ScrumMasters and Product Owners think and operate.

    And if ScrumMasters and Product Owners are from different planets, does it make sense for the two roles to be performed by the same person? Or does every Agile team even need both of these roles? Attend this talk to find out!

    This talk will further explore how we can counteract the differences in the communication, the emotional and the business needs of the two roles, and tips and techniques to promote a greater understanding between these two of the most important roles in any Agile team.

  • Liked Sheshadri Shekhar
    keyboard_arrow_down

    Facilitating truly effective "Individuals and Interactions"

    Sheshadri Shekhar
    Sheshadri Shekhar
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The Agile Manifesto is largely predicated on communication within the project context. Truly effective communication is a function of trust and empathy. 

    This presentation shows the use of a behavioral assessment model in the context of “individuals and interactions”. We first trace the formation of a behavioral-type (or pattern) and then see typical behaviors exhibited by the 15 types identified by the model. We examine the role of behavioral-pattern in creating trust within the team.

    Following this we examine the response of each personality-type to "change". As agile coaches, we have noticed that the response to the change varies from active-support to passive-resistance to active-resistance. We use the DISC model the interpret the reasons for the response.

    Finally, we try to interpret behavior of the "team" using the DISC model.

     

  • Liked Raghavendra S
    keyboard_arrow_down

    Continuous integration and delivery for Better predictability

    Raghavendra S
    Raghavendra S
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The successes of agile software development lies in delivering the workable unit of application with quality as per accepted sprint timelines and receives feedback on the shipped deliverable and incorporate the changes in the current sprint to ensure greater customer satisfaction and trust. Believing in the fact that catch early and fix issues leads to a greater predictability in software deliverable, it becomes imperative to enable developers with set of tools and accelerators which can be leveraged during development. A well-defined continuous integration and delivery process plays a vital role in enabling project teams to leverage all the tools and accelerators during development and automating the testing processes.

    However, configuring and managing a CI system at an organization level for each project is a cumbersome task. Also, writing build scripts to automate build actions requires considerable scripting expertise and time. A centralized CI platform that can abstract the complexities of configuring, managing a CI workflow along with the build scripts can ensure greater predictability of software delivery at a far lesser time. Such a platform enables automated build definition creation, to execute build application at regular interval with list of validation embedded along with the compile and build operation. The platform intended to deskill the build definition creation, ensure compliance to continuous integration process. The list of validations that could be part of the continuous integration are automated code analysis, unit testing, code coverage, deployment to multiple environments, functional, performance, security testing, etc. and organization specific validations.

  • 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 Cara Turner
    keyboard_arrow_down

    Building Creative Teams: Motivation, Engagement and Retrospectives

    Cara Turner
    Cara Turner
    schedule 3 years ago
    Sold Out!
    90 mins
    Talk
    Advanced

    How do software teams become creative? If you're not a start-up, does creativity even play a role in the business driven world of software development? Idea generation is the basis of all our work - no matter how challenging or mundane. With a scientific approach to implementing change, creativity is the basic tool we have for addressing the challenges of software development.

    This talk explores the elements of engagement and creativity along with the neuroscience of generating ideas. These give us specific insight into how employing different agile retrospective formats over the course of the product development process can extend our usual practices and develop a thinking mind-set comfortable with tackling daily work with a fresh and explorative approach.

  • Liked Michael Heydt
    keyboard_arrow_down

    Applying Lean UX to Capital Markets - Lessons From a Year of Lean UX on Wall Street

    Michael Heydt
    Michael Heydt
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The Lean UX approach to interaction design is a spectacular model for defining and implemented what is needed in appications to support the users in their jobs, as compared to technical deliverables that in the end often do not meet the needs of the users.  In this talk, I will go over strategies for applying lean UX practices to capital markets projects, adapting UX to agile processes, including executing user interviews, rapid UX design, mockups to UI prototypes, and rapid implementation through continuous delivery and end user experience / acceptance testing.

  • Mark Collins-Cope
    Mark Collins-Cope
    schedule 3 years ago
    Sold Out!
    90 mins
    Talk
    Intermediate

    This talk discusses a reference architecture for object-oriented/component based systems consisting of five strata (or layers**).

    The purpose of the talk is to show how this large-scale application model helps us to understand the overall structure of a system, how strata help us to clarify our thoughts, and how it encourages the separation of concerns such as the technical v. the problem domain, policy v. mechanism, and the buy-or-build decision - and of course why this style of architecture is relevant to ease of refactoring and software restructuring under changing and multiple requirement sets.

     

    Assuming an application is made up of a number of components, the strata proposed is based on how specific to the particular requirements of an application each component is. More specific (and therefore less reusable) components are placed in the higher layers, and the more general, reusable components are in the lower layers. Since general non-application components are less likely to change than application specific ones, this leads to a stable system as all dependencies are downward in the direction of stability, and so changes tend not to propagate across the system as a whole.

     

    ** regarding: layers
    As well as presenting the reference model, this talk also discusses and clarifies in concrete terms the meaning of one architectural layer being above another. Perhaps surprisingly, the meaning of the layering metaphor is the subject of some confusion. Specific examples of this are given in the talk - though not yet shown on the slides.

    (Note; this is suggested a 90 minute presentation however it can be extended to a full half-day, one day or two day workshop. I also have two other agile presentations which I can submit if interest is there - these cover agile planning).

  • Liked Naveen Nanjundappa
    keyboard_arrow_down

    Why not estimate? Think different for story point estimation.

    Naveen Nanjundappa
    Naveen Nanjundappa
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The Agile Community talks a lot about Estimation and need for it. A large majority have different opinions, but when it comes to teams and organizations that are transforming to Scrum, mostly suffer in group estimation and story point estimation technique. 

    Agile primarily focus on value based deliver and that doesn't need estimation. 

    This presentation enrich those audience who need estimations for their project/product development, with details that make estimates better. At the same time it doesn't advocate estimation as a must have for product development.

    Following 4 aspects will be connected to story point estimation and help audience understand the story-point estimation.

    1. Concept of Accuracy and Precession

    2. Cone of Uncertainty

    3. Story point Estimation scale

    4. Group Estimation and Relative Estimation

    Teams struggle in estimating the product backlog items. Composition of estimation: any estimate is a mix of "the known, unknown and complexity". The presentation shall also connect estimation thoughts to product backlog and the cone of uncertainty

  • Liked Johannes Brodwall
    keyboard_arrow_down

    Bare-Knuckle Web Development

    Johannes Brodwall
    Johannes Brodwall
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Can you go faster with less weight?

    We have all learned the benefit of reusing application servers like JBoss, ORMs like NHibernate or dependency injection frameworks like Spring that "solve all the plumbing code for you", but how real are these benefits really? Most developers struggle using techniques like test-driven development and refactoring effectively in their day to day project. Many developers spend a majority of their day finding out which magic incantations will make your framework solve your requirement.

    Yes, frameworks probably will reduce the size of your code base. But will their reduce the time it takes to develop that code base? And perhaps even more pressingly: How certain are your estimates when you know that a the majority of your work is to find out exactly which few lines of code you need to change by debugging, reading documentation and searching for answers on stack overflow?

    When I was first learning math, my dad told me that I didn't to use a calculator before I could do the math without it. In the same tradition, this talk builds on the premise that you shouldn't use a framework that you can't do without: I will create, live, a realistic web application without generators, without frameworks and without bullshit. Instead, I will use test-driven development to ensure steady progress to a solution with no magic.

  • 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 Arijit Sarbagna
    keyboard_arrow_down

    Quality in Code not in Management Slides

    Arijit Sarbagna
    Arijit Sarbagna
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    Agile has always challenged people with the question on how much to design upfront! It doesn't end there, it even flows in the day-to-day work of the developers & the associated Engineering Practises. We do understand the need to have a scalable design, rigid code quality checks - but who is eventually driving these? How are the architects coping with the changing dynamics of development methodolgoy? Are we really driving those practises in reality or are they finding place in management slides only?

    This session is an attempt to project how the practise of architecture is getting mis quoted/mis understood in most of the ongoign Agile projects & what has been the root cause behind them.

    We also try to come to an agreement as what should be the ideal approach towards setting up an Agile Architecture.

  • Liked Prerna Kale
    keyboard_arrow_down

    Cent Cent Business Value! A Sneak Peek at sprints from evolving design/UI, getting right priorities to delivering $$

    Prerna Kale
    Prerna Kale
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

     

    We want to share experience of working on a complex project, with deadlines set upfront and all players distributed. Perhaps argued as a complex combination to have but yet we were right there, on time enabling the new tool there. Reporting systems often have evaluation cycle that have imperative timelines to start and freeze, hence working for a huge system was not easy. Right agilist mindset with right agile practices helped us meet this. As a Product owner I jostled with eight experts using one system with some variation for their own service lines. We want to show how we leveraged the benefits of distributed teams balanced the challenges, kept the UI flexible enough to accommodate 8 expert reviews, and how our evolving architecture designed a system that had the most used and important features for the users to try hands on..

    Introspecting and sharing how we ensured Cent Cent business Value:

    - Kick off the project with eight stakeholders that got the ball rolling
    - Identifying the 30 % that was core to the business
    - Inspecting, and adapting to constant changes with modular designs
    - Getting stakeholder agree on priorities
    - Release Backlog with stories and design with validated acceptance criteria
    - Managing challenges and ensuring meeting needs seamlessly with truly distributed teams (Distributed PO/Designer/Architect/ Team/ Stakeholders)

    How important is it to dig the core 20-30% in projects with deadline upfront and ways to do that.. Prioritization techniques that enabled mutual agreement on the needs. Backlog with designs that reduced the development time. How work effectively with distributed teams, by building trust, keeping motivation and sharing the definition of done- yes we lived it and did it! We want the audience to explore it all with us and be open to take up and successfully meet the projects with distributed agile teams and tight deadlines yet agile :)

  • 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 Abhishek Kumar
    keyboard_arrow_down

    How to implement TDD in DevOps : Right and Wrong

    Abhishek Kumar
    Abhishek Kumar
    schedule 3 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    This talk will cover the pattern of following TDD when developing using Automated Configuration Management frameworks like Chef/Puppet. Real usability of Testing is based on keeping sanctity of WHAT needs to be tested WHERE. Talk will cover the same in domain of DevOps.

    This will cover the Concpetual Mapping of Unit Testing, Integration Tests and Performance Tests in reference of development under DevOps practices.

    The common mistakes that used to happen in DevOps domain was direct mapping of Business Application TDD model. Like porting of Testing tools such as rspec, cucumber for DevOps utilities and blindly implementing to show 100% coverage whether the Tests were actually justified there or not.

    We'll be seeing such examples and the correct way to implement justified Tests for your DevOps set-up.

    For example:

    Port of test packages like RSpec (puppet-rspec, chefspec) shall be used for only which cases and how they are totally un-justified for to plainly test the Resources which are just imitations without a real node.

  • Liked Sunil Mundra
    keyboard_arrow_down

    Observing and Enabling The Agile Mindset

    Sunil Mundra
    Sunil Mundra
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    Agile is actually an approach and a Mindset, whereas most people misunderstand it as a set off practices. There are umpteen examples of people implementing the Agile practices and artefacts, but are failing to get the intended positive results. This is a classic problem of ‘doing Agile’ as opposed to aiming to ‘be Agile’. The key to getting the optimal benefits is having the Agile Mindset.

    Mindset is abstract and hence one needs to understand it based on what is visible in behaviours, policies etc. The talk is about not only what these visible characteristics are, but also about what can be some of the enablers to move towards achieving the Agile Mindset. It has been proven that Leadership of an organization plays a key role in enabling the right Mindset, and hence this talk is meant for Leaders.

     

  • Sharad Julka
    Sharad Julka
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    -Open Source development depends a lot on community, their feedback,

    their suggestions, their reviews and their enthusiasm.

    -For an open source development project, the community itself is the first customer.

    -Product release for the community provides a good starting point to assess

    how the product will be accepted in the market.

    -This is very beneficial as it gives the software development team an edge over

    its competitors as it gets the pulse of the customer

    -In many ways the open source development has the culture similar to that of

    an Agile enterprise.

    -The principles guiding open source development are similar to Agile principles

    -The session presents views on above as well as how open source development projects employ agile for

    both the community development and for their own licensed version of the software.

  • 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
  • Liked Angeline Aggarwal
    keyboard_arrow_down

    Being Agile in a Non-agile World

    Angeline Aggarwal
    Angeline Aggarwal
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Software projects are all about collaboration – within teams, with external teams, external agencies, etc.Executing a project as a stand-alone team even in a sterile agile environment can be challenging. But what happens when you have to additionally collaborate with other non-agile teams to accomplish project goals?

    Non-agile teams follow different processes, have different priorities and most of all have a different mindset. How, as a Product Owner, can you plan sprint goals and milestones, get these teams to buy-in to your project vision and take time out to prioritize and help accomplish your project goals.

    In my session, I will share my experience in working with non-agile teams. I will explore the challenges that both teams face, and share practices and solutions that, if adopted, could make the end-result a win-win for all teams involved.

  • 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

     

  • Liked Shrawan Gaur
    keyboard_arrow_down

    Learn from Mistakes, Retain Your Strong Holds: Sprint Retro: Do As WE Do at John Deere

    Shrawan Gaur
    Shrawan Gaur
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    As the 12th Agile Principle states : "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.", it is quite easy to understand the importance of continuous evolvement which involves retaining learning and corrective actions.

    John Deere has started its Agile journey in year 2010 and since then has gone through various phases of transformation. Scrum teams has learnt alot and are continuously learning. Retrospection is one of very important scrum ceremony which paves path for team to advance in right direction.

    Here, I will demonstrate some retro techinques and its applications according to sprint work.

  • Liked Tarang Baxi
    keyboard_arrow_down

    The Agile ContraDictionary

    Tarang Baxi
    Tarang Baxi
    schedule 3 years ago
    Sold Out!
    20 mins
    Talk
    Beginner

    Inspired by 'The Devil's Dictionary' by Ambrose Bierce, this is a satirical look at common misinterpretations and misunderstandings of Agile principles, processes, behaviours and roles. Precise, clear (re)definitions for Exactimation, Scrumudgeon, Abuser stories, Kanband-aid, Fragile methods, ScrumLord, Rundown chart, and many more!

  • Liked Anand Ananthpadmanaban
    keyboard_arrow_down

    Agile Economics and Project Delivery

    Anand Ananthpadmanaban
    Anand Ananthpadmanaban
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    The world is expecting faster roll out of software delivery and expecting better outcomes.Agile has been getting adopted as an answer to address the expectations. The economic conditions influence any development, increasing pressure to balance CAPEX and OPEX expenditures.So the question that comes is whether software development can be governed by engineering discipline alone or we need to move to economic driven system. Establish a more real time governance, project delivery and agile economics.

    This paper shares the experience and point of view on moving to continuous software delivery from software development. It also talks about conventional governance versus economics driven at various levels i.e. organization – business –IT –customer/stakeholders.

  • Liked Pradeepa Narayanaswamy
    keyboard_arrow_down

    We're Moving to Agile: What Do I Do with My testers?

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

    As more and more organizations are transitioning to Agile, there still exist a lack of understanding on how testing fits in the Agile teams. Is it just about placing a tester in every team? How can we realign the team members including testers from being on silos to an effective cross-functional team? Pradeepa Narayanaswamy shares her insight on the key basics of Agile testing along with understanding the Agile testing mindset and testing goals. Pradeepa also shares her ideas on how to manage defects, what to measure as metrics and what to document. Learn what you need to know as a tester who are new to Agile. If you are an experienced Agile tester, review these important basics and realign the concepts that may have been overlooked or forgotten in your teams.