Re: Indicators of status project for senior management

Hi.

Can you invite them to the Sprint Review and have a face-to-face
conversation between the Scrum Team and the Senior Managers?

This is the best way for feedback versus status reports in either direction
and requires / shows commitment (and requires courage in organizations
where there is fear).

Thank you.

- mike vizdos
  Focus. #deliver

  www.implementingscrum.com
  www.michaelvizdos.com

On Fri, Jan 27, 2017 at 3:28 PM Cass Dalton [email protected]
[SCRUMDEVELOPMENT] <[email protected]> wrote:

>
>
> I used the term features because our backlog items are usually at a much
> finer granularity than is digestible by management. The term feature was
> intended to imply a higher conceptual level than the PBL item
>
>
> On Jan 26, 2017 2:29 PM, "'Steve Ash' [email protected] [SCRUMDEVELOPMENT]"
> <[email protected]> wrote:
>
>
>
> I concur with Cass on this although I prefer to use the Scrum terminology
> of ‘Backlog Items’ rather that ‘features’ – features is such a sloppy word
> and not equally understood by people that use it.
>
>
>
> Basically, you can forget RAG; the only time that you are in trouble is
> when the Must Have line goes below the End of Budget or Schedule lines.
>
>
>
> Hope that helps
>
>
>
> *Steve Ash*
>
> 
>