Four Ways to Successfully Engage Stakeholders

Slides:



Advertisements
Similar presentations
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Advertisements

Release Planning – Test Role and Responsibilities Emergence Tech Training / emergencetechtraining.com.
Agile Project Management with Scrum
SCRUM John Drew. SCRUM - overview Scrum is a project management discipline that has evolved since the early 1990s to deliver software that meets business.
NAUG NAUG Knowledge Evening – th February 2007.
User Request BAU Prioritisation process Investment Prioritisation process PM BRD Stakeholders BA BRD Product Backlog Ranked list of requirements from BRD.
Scrum 1.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Agile development By Sam Chamberlain. First a bit of history..
Michael Burnside Blog: Software Quality Assurance, Quality Engineering, and Web and Mobile Test.
What is Scrum Process? Where is it used? How is it better?
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
Copyright Robert W. Hasker. Story Review  Elements of a Scrum story:  The three C’s:  Sprintable stories:  Mechanisms for obtaining stories:
SCRUM introduction 6 April Scrum Team are known as pigs because they’re committed to delivering Sprint Goal People who are involved but not dedicated.
Process is continuously improving Have Definition of Done (DoD) DoD achievable within each iteration Team respects DoD The bottom line Delivering working,
OFFICE OF INFORMATION AND TECHNOLOGY Mobile Applications Scrum Framework November 21, :00 am (EST) Seal of the U.S. Department of Veterans Affairs.
Who is Gregg? 1 Mile
Barnes & Noble Alonda Morgan. Agile UX Agile.
Agile Scrum Development Carter Jasinski. Outline ● Introduction ● Roles ● Artifacts ● Sprints ● Uses.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
CS223: Software Engineering
Agile Methods SENG 301.
Agile Project Management and the yin & yang of
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Mrs. Starkovich’s Thank you! Upcoming Events A Peek at Our Week
Agile Project Management
Helping you succeed in promoting your club
Waterfall, Agile & Scaling Agile
Agile Training – Agile Overview
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Scrum Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
WEST LODGE SURGERY PATIENT SURVEY FEEDBACK NOVEMBER 2014.
Real Metrics for Real Decisions
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Programme Board 6th Meeting May 2017 Craig Larlee
By: By: Agile Scrum Master Online Training.
How to submit a strong application
Project & Program Governance
Rapid software development
AGILE METHODOLOGY MANAGE PROJECT USING AGILE SCRUM.
CEN 4010 Intro to Software Engineering Professor Alex Roque
Project Management and the Agile Manifesto
Mathematics Lesson 1: Money, Money, Money
How to Successfully Implement an Agile Project
Teaching slides Chapter 1.
Tips and Tricks for Using our Scripts
End of Year Performance Review Meetings and objective setting for 2018/19 This briefing pack is designed to be used by line managers to brief their teams.
Scrum Overview.
SCRUM PROCESS RELEASE SCRUM PROCESS M SCRUM ROLES
Timebox Development Instructor: Manfred Huber
Case Study: Financial Services
Frameworks in project management
Agile practices for documentation teams
Sprint Planning April 2018.
Chapter 3 – Agile Software Development
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
Introduction to Agile Blue Ocean Workshops.
Monitoring and Evaluating your School Development Plan Hollie King
27th November to 17th December
Software Development In Agile
How to deal with requirements in an Agile context?
AN AGILE DEVELOPMENT METHODOLOGY
Street Manager Training approach
Lincoln Elementary School
Speaker’s Name, SAP Month 00, 2017
Engagement Planning - Communications
Agile product development
Software Development In Agile
Product Development & Planning
Presentation transcript:

Four Ways to Successfully Engage Stakeholders Tiago Palhoto

“Thank you” to the organizers. Ademar Aguiar Catarina Carvalho Catarina Reis Dulce Domingos Filipe Correia Francisco Martins João Cerdeira Luís Ramos Miguel David Miguel Saraiva Sampaio Ricardo Martinho Teresa Carreiro And thank you for being here!

A Simple but important request… Would you please turn off your Wifi on your cell phone?

Who am I? Currently working as an Agile Trainer/coach @ Part of the Agile Community since 2001; Married, with two lovely children. Love to cook, do sports, play the drums and read…a lot!!

My contribution to the Agile Community

What’s this all about? Falar sobre a minha experiência pessoal: falta de contextualização dos stakeholders (PO incluído)

What’s this all about? Falar de como estes dados (apesar de serem de 2011) me fazem sentir que pouco ou nada mudou. 2011 – Scott Ambler - http://www.ambysoft.com/surveys/agileStateOfArt201011.html

What’s this all about? Falar de como estes dados (apesar de serem de 2011) me fazem sentir que pouco ou nada mudou. 2011 – Scott Ambler - http://www.ambysoft.com/surveys/agileStateOfArt201011.html

The four ways: Introduce the stakeholders to the framework you will use; Share the Calendar of activities; Inputs during the sprint (informal feedback); Define Stakeholders’ Schedule.

Introducing the framework

Introducing the framework It’s of paramount importance that the stakeholders fully understand your framework!

Introducing the Framework For the SCRUM framework, I always put special focus on the following items: Sprint – Small increments, early and constant feedback,deliver value. Velocity as a performance measure; Story – Definition of user story and why it’s useful. Explain the structure (the 3 C’s);

Introducing the Framework Relative and detailed estimates – Difference and when to use each. I usually use accuracy and precision to explain the relative estimates; Backlog – “Bag” where all the stuff to be built goes. The need to be prioritized; Release plan – it’s very important to mention the need to update it after each iteration based on the performance of the team.

The Calendar of Activities

Calendar of activities In 2006, I decided to start a treatment to correct a couple of problems with my jaws; Constant pain took me to the doctor to seek for help.

Calendar of activities PROCEDURES Upper Braces on November 2006. To be used until early 2010 Upper jaw surgery on January 2007 to place expander. To be used during 4 months; Lower Braces on October 2007. To be used until early 2010 Lower Jaw surgery June 2009 ROUTINE APPOINTMENTS Monthly appointment to verify Braces Weekly appointment during four months after the Upper jaw surgery;

Calendar of activities

Calendar of activities For the Calendar of Activities, I always put special focus on the following events: Planning Meeting – Make sure the stakeholders (and PO) understand their role and that this meeting needs to be prepared during the previous sprint; Story Workshop – Start preparing the next sprint by reviewing the contents of the backlog; Grooming – Explain the changes to the team so that they can give an updated estimate;

Calendar of activities For the Calendar of Activities, I always put special focus on the following events: Backlog Prioritization – Based on the estimates, the PO and the stakeholders will review the priorities; Review meeting – This is the easiest one to get PO and stakeholders on. Important to mention that bugs may show up and changes too.

Feedback during the sprint

Feedback during the sprint 1-4 Weeks Common scenario

Feedback during the sprint Some stakeholders, during the review: Feel stressed Feel lost Wary

Continuous delivery of functionalities Feedback during the sprint Feedback Continuous delivery of functionalities Feedback Informal feedback mechanism

Feedback during the sprint Key benefits for the stakeholders Less pressure Increased knowledge Self paced evaluation Self pace evaluation – Stakeholders can analyse and play with the new stuff at their own pace; No pressure – No pressure when performing this analysis to say “Yes”, as this will be later, during the review meeting; Increased knowledge – By the time of the review, stakeholders will be better prepared to deal with the implemented stories.

Define the Stakeholders’ schedule

Ok. At least now I know what can I count on and organize myself. Define the Stakeholders’ schedule Book your Mondays and Wednesdays for classes at 6pm for the next 6 months. Ok. At least now I know what can I count on and organize myself.

Define the Stakeholders’ schedule Ensures the meetings will be part of their schedule right from the beginning; Stakeholders will be able to plan their activities and prepare the meetings in advance;

Q&A