4 ms·

I think there is a balance but yeah it isn't good if no record of "where we are" exists.

steveBK123 4y ago
Yes but I think people overestimate how automatable this actually is. Where we are context depends on if the audience is - * The next developer to pick up the task where you left off * Your technical lead asking for update * Your manager needing an update for his manager * Product management wanting to know where we are on some feature * End users wanting to know when the bug fix / feature they asked for will be in their hands Everywhere I have worked, we had multiple apps/ticketing systems/etc all trying to roll up / slice & dice data to get to the above. In the end it just turns into talking to management pinging the next level below them for adhoc status. Why? Because product is too ignorant to open Jira nor maintain status themselves. Because management above the line manager level is apparently incapable of opening Jira either, let alone 2-3 levels up. Also no one wants to hire real project managers anymore to maintain all the different views & send the weekly updates they demand to receive.
- steveBK123 4y ago
  And remember, all of the above is a symptom of being in an organization where someone more important than you says "I don't have time to look at <insert reporting system>, tell me what the status of <deliverable> is". Fixing this from the bottom up is better accomplished via updating ones resume & LinkedIn profile.
- dmix 4y ago
  Are your tickets even designed/written for consumption by product/management?
  - steveBK123 4y ago
    Well they were more rigidly formatted for product consumption with Acceptance Criteria, Milestone->Epic->Story hierarchy creation to roll up to larger efforts, tags, Ready For Sprint criteria, standard story point sizing, But very little detail on how one was technically to do the task, or time spent discussing technical options & tradeoffs.

Yes but I think people overestimate how automatable this actually is. Where we are context depends on if the audience is - * The next developer to pick up the task where you left off * Your technical lead asking for update * Your manager needing an update for his manager * Product management wanting to know where we are on some feature * End users wanting to know when the bug fix / feature they asked for will be in their hands Everywhere I have worked, we had multiple apps/ticketing systems/etc all trying to roll up / slice & dice data to get to the above. In the end it just turns into talking to management pinging the next level below them for adhoc status. Why? Because product is too ignorant to open Jira nor maintain status themselves. Because management above the line manager level is apparently incapable of opening Jira either, let alone 2-3 levels up. Also no one wants to hire real project managers anymore to maintain all the different views & send the weekly updates they demand to receive.

steveBK123 4y ago
And remember, all of the above is a symptom of being in an organization where someone more important than you says "I don't have time to look at <insert reporting system>, tell me what the status of <deliverable> is". Fixing this from the bottom up is better accomplished via updating ones resume & LinkedIn profile.
dmix 4y ago
Are your tickets even designed/written for consumption by product/management?
- steveBK123 4y ago
  Well they were more rigidly formatted for product consumption with Acceptance Criteria, Milestone->Epic->Story hierarchy creation to roll up to larger efforts, tags, Ready For Sprint criteria, standard story point sizing, But very little detail on how one was technically to do the task, or time spent discussing technical options & tradeoffs.