Sorry, no proposals found under this section.
  • Joe Zachariah
    Joe Zachariah
    schedule 3 years ago
    Sold Out!
    20 mins

    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

  • Prajakta Thakur
    Prajakta Thakur
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report


    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.