Re: Indicators of status project for senior management

At my last job, we presented status as an annotated high level backlog.
Say you have 10 epics/features/high level items.  You draw 4 lines in the
BL: Completed, must-haves, estimated end of budget, and estimated end of
schedule.


Feature
------------------
Feature 1
Feature 2
Feature 3
Feature 4
--------------------------------  Features are completed to this point
Feature 5
Feature 6
--------------------------------  Features above are "must haves"
Feature 7
Feature 8
--------------------------------  Estimated end of budget
Feature 9
--------------------------------  Estimated end of schedule
Feature 10




This gives you a concise presentation of the status of the project.  If the
end of budget or schedule lines ever goes above the must-have line, you
have a problem.






On Thu, Jan 26, 2017 at 1:04 PM, [email protected] [SCRUMDEVELOPMENT] <
[email protected]> wrote:


>
>
> Hello,
>
> I have a request from my manager to prepare a model to be presented to
> senior managers on status for agile projects. Today they have a RAG status
> for three indicators: time, cost and quality (risks). Time and cost are
> based on deviation of earned value. Eg: costs exceeding 20% of planned is
> Red status.
>
> I already presented to him burn up, but that is not feasible, as he'd like
> a simple dashboard and see status of all running projects.
>
> Do you have any suggestions on that?
>
> thanks, Daniel
>
>
> 
>