Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current Restore this Version View Version History

« Previous Version 18 Current »

Sprint Goals

YSB: Complete Topic and Buildings Classification stories - COMPLETE NOT ON SCHEDULE
YSB: Close all 4.2 tasks - COMPLETE
FRMS: 3.0 Release - COMPLETE
FAS: Ingest Release 1/16 - COMPLETE
CEA: Finish Print View - INCOMPLETE
SDF: Close all Maintenance Tasks - INCOMPLETE
Arts Cal: Close all Maintenance Tasks - INCOMPLETE
FMP: FMS Med3 Upgraded - COMPLETE

YSB: Complete Topic and Buildings Classification stories -COMPLETE NOT ON SCHEDULE

 Click here to expand...

Dev: Build classification Logic Public Safety CUS-15027 - Getting issue details... STATUS - COMPLETE NOT ON SCHEDULE

Several tasks created initially that were closed - significant rework to ticket needed.

Dev Subtask

Planned

Actual

CUS-15146 - Getting issue details... STATUS

2h

2h

CUS-15147 - Getting issue details... STATUS

2h

2h

CUS-15148 - Getting issue details... STATUS

3h

3h

CUS-15150 - Getting issue details... STATUS

2h

2h

QA Subtasks

Planned

Actual

None - Dev Only

Defects

Planned

Actual

None - Dev Only

CUS-15030 - Integrate Results Page Mockup CUS-15030 - Getting issue details... STATUS - COMPLETE NOT ON SCHEDULE

Dev Subtask

Planned

Actual

CUS-15138 - Getting issue details... STATUS

4h

5h

QA Subtasks

Planned

Actual

CUS-15205 - Getting issue details... STATUS

15m

1h

CUS-15206 - Getting issue details... STATUS

1h

1h 30m

CUS-15207 - Getting issue details... STATUS

30m

30m

CUS-15208 - Getting issue details... STATUS

1h

2h

UI/UX Subtask

Planned

Actual

CUS-15376 - Getting issue details... STATUS

4h

1h

QA Subtask

Planned

Actual

CUS-15643 - Getting issue details... STATUS - Currently Blocked due to Figma vs. Template Discussions

6h 30m

CUS-15028 - Dev: Topic filter logic plumbing, power, weather - CUS-15028 - Getting issue details... STATUS COMPLETE NOT ON SCHEDULE

Dev Subtask

Planned

Actual

CUS-15159 - Getting issue details... STATUS

2h

2h 15m

CUS-15160 - Getting issue details... STATUS

2h

4h 15m

QA Subtasks

Planned

Actual

None - Dev Only

Integrate Mockup for Advanced Search buttons and forms - CUS-15029 - Getting issue details... STATUS COMPLETE NOT ON SCHEDULE

Dev Subtask

Planned

Actual

CUS-15133 - Getting issue details... STATUS

1h

2h

CUS-15134 - Getting issue details... STATUS

3h

3h 30m

CUS-15135 - Getting issue details... STATUS

4h

3h 15m

QA Subtasks

Planned

Actual

CUS-15201 - Getting issue details... STATUS

30m

30m

CUS-15202 - Getting issue details... STATUS

2h

2h

CUS-15203 - Getting issue details... STATUS

30m

30m

CUS-15204 - Getting issue details... STATUS

2h

CUS-15624 - Getting issue details... STATUS

1h

CUS-15625 - Getting issue details... STATUS

1h

Defects - 4 valid, 2 related to figma v. template

Planned

Actual

CUS-15628 - Getting issue details... STATUS

1h 35

CUS-15629 - Getting issue details... STATUS

1h 45m

CUS-15634 - Getting issue details... STATUS

1h 35m

CUS-15638 - Getting issue details... STATUS

2h 20m

CUS-15354 - Dev: Set new categories and sections to Incidents and Buildings - CUS-15354 - Getting issue details... STATUS COMPLETE

Dev Subtask

Planned

Actual

CUS-15133 - Getting issue details... STATUS

1h

2h

CUS-15134 - Getting issue details... STATUS

3h

3h 30m

CUS-15135 - Getting issue details... STATUS

4h

3h 15m

CUS-15316 - Dev: Build classification Start Tables for Logic - CUS-15316 - Getting issue details... STATUS COMPLETE

Dev Subtask

Planned

Actual

CUS-15328 - Getting issue details... STATUS

0m

0m

CUS-15329 - Getting issue details... STATUS

4h

0m

CUS-15330 - Getting issue details... STATUS

4h

3h 30m

QA Subtasks

Planned

Actual

None - Dev Only

CUS-15332 - Dev: Build classification Logic - Atletics, Building, Campus Security CUS-15332 - Getting issue details... STATUS COMPLETE

Dev Subtask

Planned

Actual

CUS-15333 - Getting issue details... STATUS

2h 30m

2h 30m

CUS-15334 - Getting issue details... STATUS

2h 30m

2h 30m

CUS-15335 - Getting issue details... STATUS

2h 30m

30m

CUS-15336 - Getting issue details... STATUS

40m

30m

CUS-15337 - Dev: Build classification Logic - Facilities Ops, IT, Outages CUS-15337 - Getting issue details... STATUS COMPLETE

Dev Subtask

Planned

Actual

CUS-15338 - Getting issue details... STATUS

2h 30m

45m

CUS-15339 - Getting issue details... STATUS

2h 30m

45m

CUS-15340 - Getting issue details... STATUS

2h

1h

CUS-15341 - Getting issue details... STATUS

45m

30m

CUS-15342 - Dev: Build classification Logic - Public Safety, Yale Alerts, Yale Health - CUS-15342 - Getting issue details... STATUS COMPLETE

Dev Subtask

Planned

Actual

CUS-15343 - Getting issue details... STATUS

2h 30m

15m

CUS-15344 - Getting issue details... STATUS

2h 30m

15m

CUS-15345 - Getting issue details... STATUS

2h 30m

15m

CUS-15346 - Getting issue details... STATUS

40m

30m

CUS-15347 - Dev: Topic filter logic Construction Fire Alarm Flood - CUS-15347 - Getting issue details... STATUS COMPLETE

Dev Subtask

Planned

Actual

CUS-15153 - Getting issue details... STATUS

2h

45m

CUS-15154 - Getting issue details... STATUS

2h

45m

CUS-15155 - Getting issue details... STATUS

2h

45m

CUS-15617 - Getting issue details... STATUS

30m

30m

CUS-15349 - Dev: Topic filter logic Grounds, It Outages, Odor - CUS-15349 - Getting issue details... STATUS COMPLETE NOT ON SCHEDULE

Dev Subtask

Planned

Actual

CUS-15156 - Getting issue details... STATUS

2h

1h

CUS-15157 - Getting issue details... STATUS

2h

1h

CUS-15158 - Getting issue details... STATUS

2h

45m

CUS-15618 - Getting issue details... STATUS

30m

30m

CUS-15351 - Dev: Topic Merge All Topic Logics filters - CUS-15351 - Getting issue details... STATUS COMPLETE

Dev Subtask

Planned

Actual

CUS-15156 - Getting issue details... STATUS

2h

1h

CUS-15157 - Getting issue details... STATUS

2h

1h

CUS-15158 - Getting issue details... STATUS

2h

45m

CUS-15618 - Getting issue details... STATUS

30m

30m

CUS-15661 - Advanced Search results page functionality - Headers Classification & Topics Deserealization - CUS-15661 - Getting issue details... STATUS NOT ON SCHEDULE

Dev Subtask

Planned

Actual

CUS-15662 - Getting issue details... STATUS

3h

2h

CUS-15663 - Getting issue details... STATUS

5h

4h 30m

CUS-15664 - Getting issue details... STATUS

1h 30m

1h

CUS-15031 - Advanced Search results page functionality - CUS-15031 - Getting issue details... STATUS NOT ON SCHEDULE INCOMPLETE ADDED TO THE SPRINT

Dev Subtask

Planned

Actual

CUS-15619 - Getting issue details... STATUS

30m

30m

CUS-15620 - Getting issue details... STATUS

7h

5h

CUS-15742 - Getting issue details... STATUS

6h

5h

CUS-15169 - Getting issue details... STATUS

8h

6h 30m

CUS-15170 - Getting issue details... STATUS

2h

0h

CUS-15171 - Getting issue details... STATUS

30m

0h

What went well? What should we continue to do?

  • Bugs were quickly identified by QA and addressed by Dev team

  • Quick UAT Feedback from George and team

  • Stories were well organized and cleanly separated

    • Developers helped lead this conversation & communication

  • Labeling helped to identify all issues related to work

YSB: Close all 4.2 tasks - COMPLETE

 Click here to expand...

Dev work was started before in-depth project planning began - all stories were present across several sprints and many defects were not refined or added to a sprint.

CUS-13587 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-14276 - Getting issue details... STATUS

2h

2d 3h 45m

CUS-14278 - Getting issue details... STATUS

1d

4d 4h 15m

CUS-15298 - Getting issue details... STATUS

2d

1d 3h

QA Subtasks

Planned

Actual

CUS-14277 - Getting issue details... STATUS

45m

45m

CUS-14279 - Getting issue details... STATUS

4h

4h

CUS-14282 - Getting issue details... STATUS

1h

1h

CUS-14283 - Getting issue details... STATUS

5h

5h

Defects - 3

Planned

Actual

CUS-15418 - Getting issue details... STATUS - No QA Subtasks

2h

3h 45m

CUS-15421 - Getting issue details... STATUS - Not Refined, not added to sprint

20m

1h 15m

CUS-15424 - Getting issue details... STATUS - Not Refined, not added to sprint

1h

1h

CUS-13588 - Getting issue details... STATUS COMPLETE

Dev Subtask

Planned

Actual

CUS-14269 - Getting issue details... STATUS

1h

1h

QA Subtasks

Planned

Actual

CUS-14271 - Getting issue details... STATUS

15m

15m

CUS-14272 - Getting issue details... STATUS

1h

1h

CUS-14274 - Getting issue details... STATUS

15m

15m

CUS-14275 - Getting issue details... STATUS

1h

1h 30m

CUS-15369 - Getting issue details... STATUS

1h

1h

Defects - 4

Planned

Actual

CUS-15259 - Getting issue details... STATUS - Not Refined, not added to sprint

1h 45m

3h 15m

CUS-15360 - Getting issue details... STATUS - Not Refined, not added to sprint

15m

1h 30m

CUS-15384 - Getting issue details... STATUS - Not Refined, not added to sprint

15m

1h 30m

CUS-15391 - Getting issue details... STATUS - Not Refined, not added to sprint, no time logged for Dev

15m

15m

CUS-13589 - Getting issue details... STATUS COMPLETE UAT NOT ON SCHEDULE

Dev Subtask

Planned

Actual

CUS-14262 - Getting issue details... STATUS

4h

2d

QA Subtasks

Planned

Actual

CUS-14265 - Getting issue details... STATUS

30m

2h 30m

CUS-14266 - Getting issue details... STATUS

2h

2h 30m

CUS-14267 - Getting issue details... STATUS

30m

30m

CUS-14268 - Getting issue details... STATUS

2h

5h

CUS-15426 - Getting issue details... STATUS

2h 30m

30m

Defects - 2

Planned

Actual

CUS-15380 - Getting issue details... STATUS - Not Refined, Not Added to Sprint, time not logged in dev task

15m

15m

CUS-15377 - Getting issue details... STATUS

  • Not Refined, Not Added to Sprint, time not logged in dev task

15m

15m

CUS-13586 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-14288 - Getting issue details... STATUS

1d

4d 2h 30m

QA Subtasks

Planned

Actual

CUS-14265 - Getting issue details... STATUS

30m

2h 30m

CUS-14266 - Getting issue details... STATUS

2h

2h 30m

CUS-14267 - Getting issue details... STATUS

30m

30m

CUS-14268 - Getting issue details... STATUS

2h

5h

CUS-15426 - Getting issue details... STATUS

2h 30m

30m

Defects - 1

Planned

Actual

CUS-15405 - Getting issue details... STATUS

3h 15m

3h 15m

What went well? What should we continue to do?

  • Communication and team meetings

  • Raising a hand when issues are taking longer than expected

  • UAT Documentation sent on time

FRMS: 3.0 Release- COMPLETE

 Click here to expand...

CUS-14958 - Search all text in a grant - CUS-14958 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-14969 - Getting issue details... STATUS

1d

1d 2h 45m

CUS-14970 - Getting issue details... STATUS

1h

2h

CUS-14971 - Getting issue details... STATUS

30m

45m

QA Subtasks

Planned

Actual

CUS-15071 - Getting issue details... STATUS

30m

30m

CUS-15072 - Getting issue details... STATUS

1h 30m

1h 30m

CUS-15073 - Getting issue details... STATUS

30m

30m

CUS-15074 - Getting issue details... STATUS

2h

2h

CUS-15498 - Getting issue details... STATUS

2h

2h

CUS-14959 - Add “Preparer” checkbox to user profiles - CUS-14959 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-14972 - Getting issue details... STATUS

3h

3h 15m

CUS-14973 - Getting issue details... STATUS

1h

1h 45m

CUS-14974 - Getting issue details... STATUS

30m

30m

CUS-15397 - Getting issue details... STATUS

1h

1h

CUS-15398 - Getting issue details... STATUS

30m

30m

CUS-15399 - Getting issue details... STATUS

CLOSED

CLOSED

CUS-15407 - Getting issue details... STATUS

CLOSED

CLOSED

QA Subtasks

Planned

Actual

CUS-15075 - Getting issue details... STATUS

1h

1h

CUS-15076 - Getting issue details... STATUS

4h

0h

CUS-15077 - Getting issue details... STATUS

CLOSED

CLOSED

CUS-15078 - Getting issue details... STATUS

4h

4h

CUS-14961 - Add the IRES column to reports - CUS-14961 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-14978 - Getting issue details... STATUS

4h

3h 30m

CUS-14979 - Getting issue details... STATUS

1h

1h 15m

CUS-14980 - Getting issue details... STATUS

30m

1h

QA Subtasks

Planned

Actual

CUS-15083 - Getting issue details... STATUS

1h

0h

CUS-15084 - Getting issue details... STATUS

2h

0h

CUS-15085 - Getting issue details... STATUS

CLOSED

CLOSED

CUS-15086 - Getting issue details... STATUS

3h

3h

CUS-15413 - Getting issue details... STATUS

1h

1h

CUS-15416 - Getting issue details... STATUS

30m

30m

CUS-15272 - Add name fields to User records - CUS-15272 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-15273 - Getting issue details... STATUS

30m

30m

CUS-15280 - Getting issue details... STATUS

30m

30m

CUS-15281 - Getting issue details... STATUS

1h

1h

CUS-15278 - Getting issue details... STATUS

45m

45m

CUS-15279 - Getting issue details... STATUS

30m

15m

QA Subtasks

Planned

Actual

CUS-15274 - Getting issue details... STATUS

CLOSED

CLOSED

CUS-15275 - Getting issue details... STATUS

CLOSED

CLOSED

CUS-15276 - Getting issue details... STATUS

CLOSED

CLOSED

CUS-15277 - Getting issue details... STATUS

CLOSED

CLOSED

CUS-15283 - Add names to current records - CUS-15283 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-15284 - Getting issue details... STATUS

30m

15m

QA Subtask

Planned

Actual

CUS-15285 - Getting issue details... STATUS

30m

15m

What went well? What should we continue to do?

  • Taking advantage of asynchronous development opportunities

  • Work was able to be completed ahead of schedule because of communication between developers

  • Clear goals around allocation and prioritization

Lesson Learned:

  • Ask more questions in refinement about specifics in implementation

    • Example: “Search all text” - is this grant entity only, or all entities?

    • Took several iterations to find desired functionality

Question: When is the right time to ask more questions about implementation?

Backlog refinement is the designated time to really dig into ticket language, acceptance criteria, sub tasks, approach, etc and ensure the team is on the same page.

Also: Don’t worry about pinging Kim if she’s not in the meeting - she holds Refinement time for questions.

FAS: Ingest Release 1/16 - COMPLETE

 Click here to expand...

CUS-11862 - Data ingest issue - CUS-11862 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-12178 - Getting issue details... STATUS https://yaleits.atlassian.net/browse/CUS-12178

7h 30m

121h 45m

CUS-12246 - Getting issue details... STATUS

3h

21h

CUS-12551 - Getting issue details... STATUS

30m

0m

CUS-15038 - Add new process for data ingest - CUS-15038 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-15039 - Getting issue details... STATUS

1d 4h

4d 1h

CUS-15223 - Getting issue details... STATUS

30m

0h

CUS-15226 - Getting issue details... STATUS

3h

3h

What went well? What should we continue to do?

  • Documentation provided by Kim helped Dev to arrive at correct solution

    • Ex “Like”, “Contains”

  • Communication with the Client - getting formal signoff on all factors

  • Providing detailed diagrams to client helped us arrive at proper solution

  • Endpoint access for Kim significantly sped up process and improved communication

  • Nico is a very helpful and responsive colleague (thumbs up)

Lessons Learned

  • Client may not use vocabulary and nomenclature used internally

  • Communicating and understanding the WHY with the client.

  • Involve other technical collaborators during initial planning phase, specifically around system architecture

    • IE, Data Services

  • Versioning must be a part of all development moving forward to help with individual deployments

  • Impromptu deployments need to be documented, go through the change process, and signed off on internally before communicated to the client.

Possible Jira Enhancement

  • Add mandatory check box for code review tickets that reflect documented standards

    • OutSystems vs. Web Development

CEA: Finish Print View - INCOMPLETE

 Click here to expand...

CUS-14899 - PDF Export Truncating data - CUS-14899 - Getting issue details... STATUS

Closed, work continued on other tasks.

Dev Subtask

Planned

Actual

CUS-14965 - Getting issue details... STATUS

4h

6h

CUS-14966 - Getting issue details... STATUS

4h

19h

CUS-14967 - Getting issue details... STATUS

30m

1h

CUS-14968 - Getting issue details... STATUS

30m

1h

QA Subtask

Planned

Actual

CUS-15240 - Getting issue details... STATUS

1h

4h

CUS-15348 - Getting issue details... STATUS

CLOSED

CLOSED

CUS-14900 - Getting issue details... STATUS

20m

1h

CUS-14901 - Getting issue details... STATUS

30m

0m

CUS-15400 - CEA - Create Printer friendly view - CUS-15400 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-15401 - Getting issue details... STATUS

2h

3h

CUS-15402 - Getting issue details... STATUS

4h

8h

CUS-15403 - Getting issue details... STATUS

30m

0m

CUS-15404 - Getting issue details... STATUS

30m

30m

QA Subtask

Planned

Actual

CUS-15414 - Getting issue details... STATUS

30m

15m

CUS-15415 - Getting issue details... STATUS

2h

30m

CUS-15680 - Getting issue details... STATUS

2h

TO DO

Defects - 3

Planned

Actual

CUS-15675 - Getting issue details... STATUS

5h 20m

TO DO - conversation in ticket

CUS-15676 - Getting issue details... STATUS

3h

2h 15m

CUS-15677 - Getting issue details... STATUS

4h 45m

TO DO - conversation in ticket

What can we do better next time?

  • Developers use Mac, Testers use Windows (Edge)

  • Issue is system and browser dependent

    • Code review can include review across browsers

  • QA and Dev could include system/browser specifics in bugs/defects

  • More in depth acceptance criteria could help limit defects/enhance code review

  • Browser Stack for testing cannot allow for downloaded Mac files

  • Screen size and standard screen resolutions must be standardized & documented for testing and Devs

  • Team needs to document standards and practices around PDFs

  • Is there a point at which we have spent “enough” time on bugs or defects?

  • Team needs additional accessibility training and collaboration with Accessibility team

  • Accessibility planning should be part of planning from the initial development

  • Inheriting applications will cause additional defects and bugs because they do not meet our initial team standards

    • PDFs, Accessibility, Visual Design

SDF: Close all Maintenance Tasks- INCOMPLETE

 Click here to expand...

CUS-14886 - SDF (AI MENTOR) Dev: Fix: Unlimited Records in Aggregates - CUS-14886 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-15095 - Getting issue details... STATUS

1h

2h

CUS-15096 - Getting issue details... STATUS

1h

30m

CUS-15097 - Getting issue details... STATUS

40m

40m

CUS-15098 - Getting issue details... STATUS

40m

40m

CUS-15099 - Getting issue details... STATUS

2h

30m

CUS-15100 - Getting issue details... STATUS

1h

30m

CUS-15111 - Getting issue details... STATUS

40m

40m

CUS-15112 - Getting issue details... STATUS

40m

40m

CUS-15118 - Getting issue details... STATUS

1h

1h

CUS-15119 - Getting issue details... STATUS

40m

40m

CUS-14889 - Getting issue details... STATUS

1h

2h 30m

CUS-14888 - Getting issue details... STATUS

30m

30m

QA Subtask

Planned

Actual

CUS-15438 - Getting issue details... STATUS

1h

TO DO

CUS-14882 - SDF(AI Mentor) Fix: Avoid Registered Role - CUS-14882 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-14883 - Getting issue details... STATUS

2h

2h

CUS-14884 - Getting issue details... STATUS

30m

TO DO

CUS-14885 - Getting issue details... STATUS

1h

TO DO

QA Subtask

Planned

Actual

CUS-14946 - Getting issue details... STATUS

1h

IN PROGRESS

CUS-14947 - Getting issue details... STATUS

0m

30m

CUS-14948 - Getting issue details... STATUS

2h

TO DO

CUS-14909 - SDF (AI Mentor) CSS in screen style - CUS-14909 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-14910 - Getting issue details... STATUS

4h

25h

CUS-14911 - Getting issue details... STATUS

1h

TO DO

CUS-14912 - Getting issue details... STATUS

1h

TO DO

QA Subtask

Planned

Actual

CUS-14938 - Getting issue details... STATUS

1h

TO DO

CUS-14940 - Getting issue details... STATUS

2h

TO DO

CUS-14813 - SDF (AI Mentor) Fix: Multiple server requests (Aggregates or actions) inside Client Actions - CUS-14813 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-14814 - Getting issue details... STATUS

2h

3h

CUS-14815 - Getting issue details... STATUS

2h

2h

CUS-14816 - Getting issue details... STATUS

2h

2h

CUS-14817 - Getting issue details... STATUS

2h

2h

CUS-14818 - Getting issue details... STATUS

2h

2h

CUS-14820 - Getting issue details... STATUS

2h

2h

CUS-14821 - Getting issue details... STATUS

2h

2h

CUS-14822 - Getting issue details... STATUS

2h

2h

CUS-14823 - Getting issue details... STATUS

2h

2h

CUS-14826 - Getting issue details... STATUS

30m

TO DO

QA Subtask

Planned

Actual

CUS-15290 - Getting issue details... STATUS

1h

0m

CUS-15291 - Getting issue details... STATUS

2h

0m

CUS-15420 - SDF (AI MENTOR) Dev: Fix: Unlimited Records in Aggregates Part 2 - CUS-15420 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-15101 - Getting issue details... STATUS

40m

40m

CUS-15102 - Getting issue details... STATUS

40m

40m

CUS-15103 - Getting issue details... STATUS

40m

40m

CUS-15104 - Getting issue details... STATUS

40m

40m

CUS-15105 - Getting issue details... STATUS

40m

40m

CUS-15106 - Getting issue details... STATUS

40m

40m

CUS-15107 - Getting issue details... STATUS

40m

30m

CUS-15108 - Getting issue details... STATUS

40m

30m

CUS-15109 - Getting issue details... STATUS

40m

30m

CUS-15110 - Getting issue details... STATUS

40m

30m

CUS-15422 - Getting issue details... STATUS

30m

30m

QA Subtask

Planned

Actual

CUS-15439 - Getting issue details... STATUS

1h

TO DO

What can we do better next time?

Arts Cal: Close all Maintenance Tasks- INCOMPLETE

 Click here to expand...

CUS-14776 - Arts Calendar (AI Mentor) Server Requests in Client Events - CUS-14776 - Getting issue details... STATUS

Closed, significant time spent on issue deemed irrelevant

Dev Subtask

Planned

Actual

CUS-14777 - Getting issue details... STATUS

30m

30m

CUS-15359 - Getting issue details... STATUS

16h

34h 30m

CUS-15671 - Getting issue details... STATUS

30m

30m

QA Subtask

Planned

Actual

CUS-15778 - Getting issue details... STATUS

1h

1h

CUS-15779 - Getting issue details... STATUS

1h

1h

CUS-14778 - Arts Calendar (AI Mentor) Remove Inline CSS style - CUS-14778 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-14779 - Getting issue details... STATUS

30m

30m

CUS-14923 - Getting issue details... STATUS

2h

4h

CUS-14924 - Getting issue details... STATUS

30m

0m

QA Subtask

Planned

Actual

CUS-14954 - Getting issue details... STATUS

2h

2h

CUS-14956 - Getting issue details... STATUS

2h

2h

CUS-14803 - Arts Calendar (AI Mentor) Remove Styles from Page sheet - CUS-14803 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-14804 - Getting issue details... STATUS

30m

0m

CUS-15195 - Getting issue details... STATUS

4h

6h

CUS-15672 - Getting issue details... STATUS

1h

1h

QA Subtask

Planned

Actual

CUS-15776 - Getting issue details... STATUS

1h

1h

CUS-15777 - Getting issue details... STATUS

1h

0m

What can we do better next time?

  • Need to be prioritized appropriately

  • How can we make it clear who “owns” a ticket in its current state?

  • QA Analysis missing on certain tasks

FMP: FMS Med3 Upgraded - COMPLETE

 Click here to expand...

CUS-15307 - CUS-15307 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-15309 - Getting issue details... STATUS

8h

1h 20m

CUS-15308 - Getting issue details... STATUS

16h

4h 12m

CUS-12412 - Getting issue details... STATUS

6h

2h

CUS-12413 - Getting issue details... STATUS

4h

1h 25m

 CUS-15463 - FMP fmsMED3 upgrade prep & Support - CUS-15463 - Getting issue details... STATUS

Dev Subtask

Planned

Actual

CUS-15466 - Getting issue details... STATUS

8h

2h 10m

What went well? What should we continue to do?

  • Making stories smaller that have tasks that can be finished

  • Lots of prep work for the work ahead of time led to success

Issues In To-Do

 Click here to expand...

CUS-13231 - Getting issue details... STATUS

CUS-15363 - Getting issue details... STATUS

CUS-9691 - Getting issue details... STATUS

CUS-13052 - Getting issue details... STATUS

What happened?

  • How do we know what should be removed from the sprint?

  • Should we have deadlines for specific tasks?

    • If things haven’t been stated by X date, should they be removed?

  • All team members are responsible for looking at these tasks & bringing them up

Key Takeaways to improve team accountability:

  • Goals and tickets are a team commitment

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.