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

  • 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

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

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

  • Michael O'Reilly
    Michael O'Reilly
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Intermediate

    Test Requirement Driven Development(TREDD) places a renewed emphasis on quality and accountability, and provides the insight to allow your product development and management teams to make the necessary changes in order to produce outstanding quality products on schedule, in a cost-efficient and highly collaborative manner.

    What separates TREDD from other development methodologies like TDD (test driven development), ATDD (acceptance test drive development), or BDD (behavior driven development), is the status of the test requirement when the product development lifecycle concludes.

    Test Requirement status is the breakthrough element that allows test requirement to provide an objective measurement to the quality of the product development team, so that adjustments can be made for subsequent product development iterations that will ensure quality improves, as well as increase the effectiveness of the product development team.

    Come and learn how your TREDD will catalyze your SCRUM team toward greater capabilities, quality, accountability, and satisfaction!

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

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

  • 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 Swarnalatha Ashok
    keyboard_arrow_down

    Performing Advanced Research in IT Topics using Agile methodologies

    Swarnalatha Ashok
    Swarnalatha Ashok
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    This paper summarizes the experience & outcomes derived out of running  an Advanced Research elective using agile methodologies for MTech (Software Engineering) students of ISS – NUS. Using Agile way of development for exploratory research work is a unique idea using which we successfully deliver several student research projects every year. The paper would document the results of applying various agile management approaches ( like SCRUM) and engineering techniques ( TDD, Continuous Integration, Refactoring) to exploratory research work and argue on the benefits of using agile approach as against traditional software development approach for academic student exploratory research work. Evidences to show how agile techniques successfully help in doing exploratory projects would be produced. Further, the interesting aspect of how Agile techniques could be used in academic teaching work to stimulate student interest in the subject would be explored.

    Takeaways for participants attending this session:

    • Understand how agile methodologies can be used to perform exploratory research work
    • Provide a framework for conducting applied research work using agile methodology
    • Critique the suitability of Agile techniques for student research work
    • Explore opportunities for expanding the scope of agile methodologies to performing research work in industry.