No surprises on Demo

[Iurii Zhuppan]

Hi all,
what is the best way to avoid surprises on Demo?

BR,
Iurii.

[Embrenchia Snyman]

Meet your sprint commitment and make sure the team does a complete dry run an hour or two before demo starts. Dont show anything that did not meet acceptance criteria.

THE BIG KAHUNA
Sent from my iPhone

> --
> You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
> To post to this group, send email to scruma...@googlegroups.com.
> To unsubscribe from this group, send email to scrumallianc...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/scrumalliance?hl=en.
>

[Howard Sublett]

The PO should have seen everything prior to the Sprint demo. Show progress as it's made, then the demo is the culmination of all that was done. 

In teams I've worked with, I've never wanted to walk into a demo for things I have never seen.  The few times it happened, it was a surprise. ( and not the.."ooooh, happy birthday" type )

Get feedback early and often. 

Howard Sublett

howard...@gmail.com

Follow ME on twitter @howardsublett

Find me on Skype @ howard.sublett

[mj4s...@gmail.com]

Test the product thoroughly. Take on smaller features until the team knows how to test the product thoroughly. Keep the Product Owner involved during the Sprint. Avoid branching. Work in a team room. Use pair programming. Hire good people and reduce management practices that make them leave.

--mj

Sent from a phone that often corrects words I tapped to words I may not have meant.

[Pierre Neis]

I understand your POV but this not "transparent" for the stakeholder how did they see the complexity of the development .

On my side, I'm more straight and I do not a demo but real inspect-adapt during the demo. When I am playing the PO and reject some items, then I am the bad guy and never the team .

 Pierre Neis

Mobile Device

[Iurii Zhuppan]

Hi Howard,
what do you think about doing an internal Demo(within a team), before
having it with customer?

BR,
Iurii

On Feb 14, 6:58 pm, Howard Sublett <howardsubl...@gmail.com> wrote:
> The PO should have seen everything prior to the Sprint demo. Show progress as it's made, then the demo is the culmination of all that was done.
>
> In teams I've worked with, I've never wanted to walk into a demo for things I have never seen.  The few times it happened, it was a surprise. ( and not the.."ooooh, happy birthday" type )
>
> Get feedback early and often.
>
> Howard Sublett

> howardsubl...@gmail.com

[Abhilash c]

Few suggestions from my side

• Scrum is transparent. We have a daily scrum (planning) meeting. This is not a mere status update.If the team feels that some of the committed PBI's cannot be delivered then it should be notified to PO. Scrum Master should ensure that this information is passed accurately to all the stakeholders (if required).
• Do a thin vertical slicing of your stories.
• Team should swarm over the highest priority PBI. ( Both development and testing should be finished before the second PBI is taken). This ensures that at least one PBI is delivered successfully & which meets all the acceptance criteria.
• Ensure that you have automated unit test cases & smoke test cases ( it will be great if you have automated regression test cases also). This will ensures that the all parts of the application works & nothing is broken after the latest code changes.
• Scedule a dry run of the PBI before the actual Sprint demo.

 

Regards

Abhilash

http://www.linkedin.com/pub/abhilash-chandran/19/b49/2b2

http://thetechjungle.blogspot.com/

  

 

To love when it can be Lost...

To Go on even when Progress seems futile,

To believe with every Fibre in ur body

To Live....To Hope... and to NEVER GIVE IN

 

 

 

[Howard Sublett]

Well, 

Transparency of the progress of the stories should be something that is inherent within the team.  I wouldn't think that you need " yet another meeting" to practice a demo. The teammates should be working together daily to ensure that the stories meet the definition of done, and when they do, the PO should be pinged to take a peek. 

lurli, What do you think is the core reason you are having this issue/question?

Howard Sublett

howard...@gmail.com

[Pierre Neis]

Ask myself: isn't this a question when the PO is not working within the team?

Pierre E.  NEIS, csp

Operational Excellence Consultant @ coPROcess S.A. │ Scrum & Lean Coach   

M: +352 / 661 727 867│ Meet with me: http://meetwith.me/pierreneis

Owner of the "Product Owner's Help Desk"

Contact me: pierr...@gmail.com pierre.neis

Latest tweet: @JPRaffalli pfff... regarde du côté du Hoshin Kanri: True North et modélisation A3. INtel. orga = dyn de groupe + objectifs Follow @elPedroMajor Reply Retweet   13:32 Feb-15

Save a tree - kill a beaver

Get a signature like this. CLICK HERE.