Vanilla Agile Risk Management- Flavored with some traditional practices

In traditional risk management process, a complete list of potential risks with their priority and a plan to mitigate them is prepared upfront. A lot of time and effort is spent towards these hypothetical risks both in upfront planning and in ongoing monitoring and discussion.

While in Agile, the process is rather emergent in nature. The realization of risk occurs quickly and abruptly. Team gets a sense of it at the earliest possible stage, delay time is less as the risk gets highlighted in the daily stand up, review, retrospectives or release/sprint planning meetings. It is more a real time thing in Agile. But are an application of these Agile practices enough to manage risks in an Agile bound project? Or with little adjustments can the traditional risk management be more powerful with Agile methods?

The session will contain a comparative analysis of risk management in both the methodologies, some real life examples, case studies and how the traditional risk management process can be tailored fit for Agile. It will be a talk cum open discussion session.

 
2 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Talk Presentation Case Study and Open Discussion

Learning Outcome

Better understanding of Risk Management in Agile projects. How can the traditional risk management process be customized to be Agile fit.

Target Audience

Scrum Master, Product Owner, Scrum team, Agile enthusiast , Evangelist

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Harikrishan Verma
    keyboard_arrow_down

    Thinking beyond - Getting out of silos

    Harikrishan Verma
    Harikrishan Verma
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    We are engineers and we know how to write code.

    We are QA engineers and we know how to test an application or product.

    There are so many roles and so many perspective about the product / application team is building. Everybody is right in their perspective. Then the question is....are we/they missing something?

    This session is going to explore the perspective beyond the perspective of an individual in team. We will try to move from individual perspective to a common perspective which is so much critical for each individual. We will talk about the user perspective and how it is important to get the 'out of box' picuture over a 'in side box' picture.

  • Liked Harpreet Singh
    keyboard_arrow_down

    Agile Product Development : Entrepreneurial Way

    Harpreet Singh
    Harpreet Singh
    schedule 2 years ago
    Sold Out!
    30 mins
    Talk
    Intermediate

    Entrepreneurship in product development is all about raising agile concepts to entrepreneurial level in a way that would clinch success by innovation, autonomy, proactiveness, risk-taking and other characteristics associated with entrepreneurship. 

    The present paper describes briefly how to make a Agile product development approach as entrepreneurial. An entrepreneur has high level of personal ownership and this is due to the fact that an entrepreneur understands that failure is not an option, so this approach of personal ownership sets performance standard high. Similarly entrepreneurial project manager understand that if the project fails then the organization fails. This paper also talks about three main aspects of entrepreneurial project management which are entrepreneurial orientation, entrepreneurial management and entrepreneurship strategy.

  • AnkitTandon
    AnkitTandon
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    -The Sprint Planning meeting is just too long and never finishes on time.

    -I finished my tasks on time, the story couldn’t be completed as there was a dependency on him. I just didn’t have time to follow it up. Not my fault.

    -Yet again, there are left over items in the sprint. We couldn’t finish all the committed stories as some of them were too complex for their correct effort complexity estimation.

    -Ohh Gosh, once again the priority of the tasks have changed in the middle of the sprint, there are new urgent items that have to be done. My sprint commitments have gone for a toss.

    -We moved to Agile from waterfall and it has been few sprints into it, though even here vision is unclear, requirements are evolving and our sprint commitments are failing. Velocity is just been a number, Burn down graphs conclude nothing concrete and useful.

    -How do we cater support/maintenance work with Scrum?

    Does any of the above statement sound familiar to you, if yes probably it is the time to evolve and adopt KanScrumBan wrapped around XP practices.

    KanScrumBan is the combination of Kanban and Scrum and uses the best features of both. While Scrum framework helps the software development teams to self-organize, collaborate, improve efficiency constantly, work in small iterations, and avoid management overhead, applying lean methods like Kanban , flavored with XP practices can extend these benefits.

  • Liked Mohit Jain
    keyboard_arrow_down

    Nothing beats a small self organising Agile team

    Mohit Jain
    Mohit Jain
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    a combination of 3 games which demonstrate the importance and efficacy of a self organising small team.

    The session also explains the "Law of Diminishing Marginal Productivity" along with other agile concepts.