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

 

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 :)

 
6 favorite thumb_down thumb_up 4 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

 

1. Brief Introduction of the Client, Project and team player roles

2. Start Sharing the experiences:

i) Focus on how to kick off project and share the techniques used that were appreciated and some dont's, also establish stakeholders understanding

ii) Next step but crucial- Prioritization and deriving the 30% core features that finds the way in the backlog also present the challenges and effective ways to manage them

iii) Brief desciption of user personnas we were dealing with their nature of business and how to leverage these in stories (ensuring we built what was needed)

2. Ask audience to share some challenges they faced with multiple SME's and distributed teams

- Present how we managed stories with distributed and large team ensuring story independence and zeroing impediments and address the challenges shared by the audience

- Share the tools used for designing, stories, prioritization, highlight agile ceremonies that were most useful

4. Recap the learning lessons and quick retrospective of the talk with audience

5. Close with Q&A

Learning Outcome

 

In this talk we will present how as a Product Owner and UI designer we moved through various sprints that helped us achieve the business goals (that matters!!)


1. How to and What in the Kick off meeting are the enablers (Tools and Techniques used)

2. How to use User Peronnas in designing the stories and split it- how is the user using the feature, role/responsibity  (Story content that helps team to deliver value at speed)

3. How to know and dig out the core 30% features that are most useful to the business, Ask and weigh (What and What not)

4. How to get all SME's agree to priorities especially when working with multiple experts, Do's and Donts (Cliassic way-Must Have and how to propose its acceptance by all, few techniques we tried and worth sharing)

5. Reap the advantages of distributed team and how to manage the challenges ( How to keep team motivated, feel connected, share the load and here you go..)

All said audience will benefit from the talk and our experience sharing the Do's and Donts will help them have an open mind of having distributed teams and deliver high value!

Target Audience

Product owners, UI Designers, Distributed development teams

schedule Submitted 4 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • AgileSattva Consulting LLP
    By AgileSattva Consulting LLP  ~  1 year ago
    reply Reply

    Hi prerana,

     Would like to know the core take away of this talk? I see it as scrum based development. You also mentioned about SMEs in the team, in what reference are you going to connect SMEs with agile teams? Is it to say to make teams cross functional or to leverage their knowledge base ? Please help me understand this!

    Deepak

    • Prerna Kale
      By Prerna Kale  ~  4 years ago
      reply Reply

      Hi Deepak,

      Thanks a lot for your comments.

      Yes we are doing this project using scrum. Core take away is how effectively big teams (9 team members), distributed, can deliver the needed value. This can be done only when right from the kick off teams adopt best practices, remain flexible to adopt to change, and focus on value! We will highlight all the impediments faced and the steps we took to acheive our target

      Please note that the Subject Matters Experts here are the experts from business (Super users) that helped team design the tracking tool. They are not part of development but sponsors or stakeholders, who set the priority and derived value.

  • Nitin Ramrakhyani
    By Nitin Ramrakhyani  ~  4 years ago
    reply Reply

    Hi Prerna,

    What you described looks like a very interesting case study. Though in past what we have seen typically with case studies is that such talks become either very interesting or very monotonous based on the presentation structure, and presenter's delivery style. How do you plan to make it engaging? Can you share your deck( or an outline with few key slides) to help the review team in assesing this against other proposals?

    The link that you have provided lands on the generic Agile tour page. Can you point to your specific presentation? Or may be upload the deck on slideshare/ dropbox and point to us.

    Will look forward to hear more on this. 

    Thanks,

    Nitin

    • Prerna Kale
      By Prerna Kale  ~  4 years ago
      reply Reply

      Hello Nitin,

      Thanks a lot for your comments. Please note that I have updated my previous presentation links, posted on slide share.

      As my deck is in progress, I will get back to you at earliest and share a draft version.

      At a high level we are going to present impediments faced and how quickly we overcame those with handy designs, how open source tools helped us acheive that faster.

      We intend to ask audience the problems they face in such projects upfront which will be not very different and relating them to our project will share effective ways of resolving these.

      We will also share an Agile Playbook  that we have coined and refer in our projects.

      Thanks again for your comments, really appreciate.

       

       

       


  • Liked Naresh Jain
    keyboard_arrow_down

    Naresh Jain - SAMPLE PROPOSAL - Product Discovery Workshop

    Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 4 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 Amoli Upadhye
    keyboard_arrow_down

    Amoli Upadhye - Scale up Agile - Cheers to complex, systems integration mega - projects!

    20 mins
    Experience Report
    Intermediate

    Large systems integration projects form a large majority in typical corporate IT departments. With growing agile methodology adoption and its proven success rate in small / mid – sized projects there is a strong interest in case studies where teams have scaled Agile for XL size project execution

    Such large integration projects warrant natural complexities and teams rely on scaling existing agile practices to be able to up their game. As these projects are high risk / high value candidates, it is critical that project teams deliver them smoothly while rallying various stakeholders involved.

    This session would describe how agile principles can be elastic enough to help teams achieve just that!

    It describes exactly which agile principles have helped me (more than others) to influence my Product Owner-ship on my big, fat COTS application product tied to many upstream / downstream systems and even more stakeholders

  • Liked Yashasree Barve
    keyboard_arrow_down

    Yashasree Barve - Why can’t Enterprise have all the Fun? –Tales from Enterprisy DevOps Land

    45 mins
    Case Study
    Intermediate

    In the age of continuous deployments, where Googles and Facebooks of the world push newer features every now and then, without any down time to millions of users! Enterprises and Users of internal IT systems within Enterprise are still stuck with old time consuming processes that take ages to churn out new features to business. Why can’t Enterprises have this fun!


    This is a story of an Enterprise that adopted and got mature in its Agile Adoption. The sponsors could see value every sprint, but it took time to translate this value to end users. Drive to sustain agility as well as getting things out to end users quickly needed to take a great momentum.


    Experimenting with DevOps came as a natural extension to this Agile-Scrum adoption. We would like to talk about the how the idea of DevOps implementation in this Enterprise originated, the various challenges met at the initial stages, carving the road map and our journey. We would highlight the benefits that we reap out of this effort as well as share best practices from what we have learnt.

  • Liked Bhuwan Lodha
    keyboard_arrow_down

    Bhuwan Lodha - Building a Team Backlog: The Power of Retrospectives

    Bhuwan Lodha
    Bhuwan Lodha
    VP - Digital
    McKinsey & Company
    schedule 4 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    “Inspect and adapt” is one of the basic tenets of continuous improvement, and agility in general. Holding retrospectives is one of the core processes that allows teams to look back and reflect on their progress. However, over time, teams may focus only on the product work and lose interest in their own improvement as a team. Kanchan Khera and Bhuwan Lodha believe that one approach to solving this problem is to bring the rigor, structure, and discipline we use for maintaining healthy product backlogs to team improvement by creating a “team backlog”—items the team needs to do to improve itself. The team backlog introduces three keys to successful and sustainable team improvement—a structured framework, visibility of its impact, and creative ways for building the backlog. Just as a healthy backlog is the basis for a great product, so a healthy team backlog helps create great teams.

  • Liked Vibhu Srinivasan
    keyboard_arrow_down

    Vibhu Srinivasan - Working at a lean startup

    20 mins
    Experience Report
    Beginner

    I have had the oppurtunity to build and be part of a few successful and failed startups. One such succesful startup was my association with a startup called Evri.com. I have also consulted as a developer and coach for a gaming company called BigFishGames which went to become a largely succesful gaming company making one game a day today. 

    In this session I would like to tell the story of what happened at Evri and Big Fishgames that made them succesful. 

    This is a lessons learned, observatiosn shared being part of this startup as a developer. This session also looks at what makes a good product. Is product creation a pure idea of a bunch of geeks working together or something more than that. 

     

    Come see and learn

  • Liked Sarika Nagvekar
    keyboard_arrow_down

    Sarika Nagvekar - Learn the knack of implementing distributed scrum in workplace

    45 mins
    Case Study
    Intermediate

    Nowadays most of the projects have more than one team working on them also the team members are distributed at varoius sites.
     
    The knowledge of working with agile distributed team is essential in the current scenario.
    In this session We would like to focus on a case study for gaining more insights on how to scale and how to work with agile distributed teams.

    - Manage cordination with two or more teams.

    - Conduct iteration planning and syncrozise work, irrespective of the number of teams.

    - Probe the varoius challenges facing distributed teams and resolve them. (Example Lack of Communication, Minimum Team Overlap, Requirements Discontinuity, Cultural Barriers).

    - Achive good team allocation, how to interacte with team members, and how to coolaborate and choose the best meeting timings across all time zone.

    - Apply immediate practical advice, where ever the teams are distributed.

  • 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 Prajakta Thakur
    keyboard_arrow_down

    Prajakta Thakur - Avoiding Common Scrum Mistakes : A Chicken & Pig Story

    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 Kanchan
    keyboard_arrow_down

    Kanchan - Come! Take a plunge with us into the world of Self Organization!

    Kanchan
    Kanchan
    Portfolio Manager
    McKinsey&Company
    schedule 4 years ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    In agile teams there is a belief that the teams self organize. But do we really understand what this really means? The scrum guide simply says three things autonomous, self transcendent, cross functional.

    In this interative workshop we will experience what self organization is all about via a fun filled game. You will go back with key learnings through your own experience. 

    This session will be a combination of audience participation in activities, discussions combined with presentations and loads of fun!

    This interactive game session is for anyone who wants to learn more about  being self organized and what makes the self organized teams tick.

  • Liked Angeline Aggarwal
    keyboard_arrow_down

    Angeline Aggarwal - Being Agile in a Non-agile World

    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 Yashasree Barve
    keyboard_arrow_down

    Yashasree Barve - What Works and What Not! A Portfolio Lead Retrospects

    20 mins
    Case Study
    Beginner

    Enterprises are complex, and so are the development groups within those. Being agile definitely enables the software development groups to deliver high value and high quality software with speed for even within an Enterprise.

    However legacy applications along with the overall Enterprise landscape pose its own challenges that are outside of the scrum framework to solve. Multiple Small scrum teams though working on separate applications need to be cohesive with a big picture. As a portfolio lead, who owns multiple applications and teams related to a portfolio within an Enterprise is a Chicken in scrum terminology. The expectation from the role is that of leader, scrum master as well as an Architect providing technical and functional oversight to the teams within the portfolio. The idea is to be a leader and not a manager in the true spirit of scrum.

    This session is about a retrospective of my work life as a Portfolio Lead who takes care of multiple scrum teams, and applications. I would like to speak about the top 3 challenges faced such as Scaling Production Support / Knowledge Retention for applications delivered through Scrum, Impact of Organizational Transformation initiatives on the scrum teams, and Multiple Stakeholder Expectations / Conflict Management through real life examples of my work. I would retrospect what I did, and discuss and debate what worked well, and what did not during this journey of mine.

  • Liked Yashasree Barve
    keyboard_arrow_down

    Yashasree Barve - Seven tales from an Ever-invigorating Agile Development Group

    45 mins
    Case Study
    Intermediate

    The constant quest in one’s mind to find Nirvana, of excelling the way we work, is never ending. Starting to do scrum is only the beginning of 'Being agile'. 'Being agile' attributes to constantly re-inventing and improving the way we develop software.

    We would like to present a case study of a development group that has adopted agile, and not shied away from trying newer things to keep scrum adoption true to the spirit of agile. We would discuss seven most powerful initiatives we practised over last 6 years to keep our developers and business excited about being agile and maximizing business value delivered. These initiatives defined the way we constantly evolved, got the new joinees of this group into the culture of agility and ensured that we are relevant to the need of hour.

    This talk would comprise of motives behind thinking about these initiatives, vision, road map as well as the way we executed them by engaging our whole development group. We would also like to highlight challenges we faced, and the benefits we derived out of these initiatives.

  • Liked Manish Sinha
    keyboard_arrow_down

    Manish Sinha - Building High Performance Distributed Scrum Teams

    45 mins
    Experience Report
    Intermediate

    (anonymous)

    Working with distributed teams is a necessity driven by globalization and outsourcing in today’s business world. Being effectively agile with these distributed teams is always a challenge. The challenges multiply when such teams consist of team members from different cultures working thousands of miles apart. Organizations are required to have teams that perform despite of challenges faced by such teams. They need to adapt to stay in business. But to get ahead in business, only adaptation doesn’t
    help, they need innovation as well.
    The session doesn’t cover any theoretical part of Agile but an “all practical”
    approach that has been tried, tested and verified. This session talks about how challenges with distributed teams can be transformed into opportunities for building high performance Scrum teams in distributed environment. The session shares best practices and lessons learnt with execution of Scrum in highly distributed team covering over seven different locations across geographies.
    The session will closely look at common challenges faced by distributed Scrum teams and how a simple restructuring of such teams can resolve many of these challenges. The session will put forward effective ways of building high team synergy in a cross cultural environment. The session will also cover few simple ways of using Lean techniques to identify potential improvement areas and to make impactful improvements.