Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 11 Next »

  Info About This Page

What is this page

A (mix of high-level / detailed) log of what has been accomplished by me, for a given week

Why create it?

I decided to do this for several reasons... The key Idea/intention/motivation behind this was threefold:

  1.  Anyone with vested interest can "watch" this page and get updated with what's going on with things that I am working on, their progress (i.e. where we are with respect to a given project) etc.
  2.  As a result of #1, above, the status update meetings can be streamlined and made more efficient in terms of meeting time, respecting everyone's (already limited) time
  3.  Year-end task of compiling the list of  Activities an d Achievements will go a lot smoother (smile)

Not to mention, I was tired of scribbling notes in Notepad

Stay informed

I highly recommend " watching " this page, if you have vested interest, as doing so the system will send an email showing a diff (along with a short note, if one is provided when updating this page) of what was added/removed/changed etc.

 Status Update Conventions
  1.  The start date is the same as the previous week's end date, as the status update happens in the middle of the AM
  2.  The previous week's updates shall NOT be updated, if they happen  after the status update. Rather, they shall be included within the next status update log
    • To understand this better, consider the following sequence of events as an example:

For week of   -  

1 Tasks A - D are accomplished.

2 Task A - D are mentioned within the update log of   — .

3 Status update meeting occurs.

4 Task E gets accomplished sometime during the day following Status update meeting.

5 Task E, then, gets included in the next status update's log of  —  

Conversely, if there are any clarifications/typos etc. (in essence, anything related to clarifying Tasks A - D, so that the reader has a clearer understanding, they will be updated in that week's update log (in our example, that would be the Update log of  —   

Therefore, to address this scenario, I have intentionally implemented Status Update Convention #1, above.



 Table Column Heading Key
  • Priority:
    • For a specified week, what was (a specified) project's priority in relation to other projects for that specified week
    • Project's priority may change from week to week; this is dependent upon a combination of factors such as: Go-live date, an urgent request, production application (critical) bug, management's direction, etc.
  • COVID-19 Related?
    • This column will have a (tick), iff a project/task is in response to the (currently ongoing) COVID-19 pandemic
  • Project:
    • Overarching project
  • Functional Stakeholder:
    • This column mentions the individual from functional area (non-IT)—the "customer"—who is the primary interface for that project and for gathering requirements (by either myself or a fellow IT colleague).
    • For certain projects, this column may list either a University division or a department
  • Requested By:
    • This column only mentions individuals from the functional area and only if the requesting individual is not the same as the customer
  • Updates:
    • (High level / detailed) accomplishments / participation / contribution towards a given project


Week OfUpdate Log

 —  

Weekly Priorities At-a-Glance


Monday  
Tuesday  
Wednesday  
Thursday  
Friday  


  1.  Everbridge
  2.  PS Payroll
  3.  HR UCPEA Reclass


  1.  Everbridge
  2.  PS Payroll
  3.  HR UCPEA Reclass


  1.  HR UCPEA Reclass
  1. HR UCPEA Reclass

Jira & Confluence may/will interject the priority list, as necessary for ticketing/documenting purposes


PriorityCOVID-19 Related?Project

Functional Stakeholder

Requested ByUpdates
1(tick)EverbridgeJeremy Friedman
  • Team regrouped prior to training day of ;
    • Implemented solution was discussed
    • Two Notification Templates were set-up
    • Testing of the new role was performed
    • General Q's and A's regarding Everbridge
  • Following two guides were created:
    • "How to Send Notifications"
    • CSV file format/requirements
2

Public Safety Payroll Application

UConn Division of Public Safety
  • Resumed Payroll troubleshooting with Ruben
    • Was able to figure out the bug and resolved it offline; will be doing a code walk-through to show where the problem was and what was done to rectify it
3
HR - UCPEA Reclassification FormJessica Bowcock
  • Meeting scheduled for 
    • Discuss timeline and pending tasks
4
SDLC (Documentation / Ticketing / Stash)

Created the following on Confluence—

Following tickets were created/updated and subsequently closed out upon completion on Jira—

  • Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Converted  Unable to locate Jira server for this macro. It may be due to Application Link configuration. and  Unable to locate Jira server for this macro. It may be due to Application Link configuration. sub-tasks to issues, thereby removing them from EVER-9 ticket, as the implemented solution did not require modifying the generateFeedFile code.

5
Leap - General


 —  

Weekly Priorities At-a-Glance


Monday  
Tuesday  
Wednesday  
Thursday  
Friday  

  1.  Tax & Compliance - FNI
  2.  Everbridge 
  3.  HR UCPEA Reclass Form
  1.  Everbridge
  2.  HR UCPEA Reclass


  1.  Everbridge
  2.  Payroll
  3.  HR UCPEA Reclass


  1. Everbridge
  1. Everbridge

Jira & Confluence may/will interject the priority list, as necessary for ticketing/documenting purposes


PriorityCOVID-19 Related?Project

Functional Stakeholder

Requested ByUpdates
1(tick)EverbridgeJeremy Friedman
Completed the task on  
2

HR - UCPEA Reclassification Form

Jessica Bowcock

3
Public Safety Payroll ApplicationUConn Division of Public Safety

4
SDLC (Documentation / Ticketing / Stash)

Everbridge task was documented in its entirety—

5
Leap - General


 —  

PriorityCOVID-19 Related?Project

Functional Stakeholder

Requested ByUpdates
1(tick)EverbridgeJeremy Friedman
  • Quarterly UConnALERT Advisory Group meeting
2

Tax and Compliance - Foreign National Information form

Laura HouseElizabeth Solecki
  • Observed functional team started testing on  
  • Made updates to both the source PDF, as well as the Leap form UI, per user feedback; last set of updates were addressed by  
    • Customer team notified; reiterated the importance of testing, as it is not being heavily tested for all different scenarios that the form can produce based on user answers to the form questions
  • Customer gave final approval for going live on  
  • Pre go-live steps completed
3

HR - UCPEA Reclassification Form

Jessica Bowcock
  • Proposed, and as was accepted by customer, have scheduled a tentatively recurring weekly meeting for project updates
  • Expanded Union Requirement #2 to include: Alternate Reviewer for Supervisor, Manager, and Alternate Reviewer for Manger
    • The expansion of role should work the same as it does for "Deny Request by Supervisor"
  • Did a walk-through of the changes; specifically, the following was covered:
    • UCPEA/Union Rule #2
      • Deny Request by: Supervisor, Alternate Reviewer for Supervisor, Manager, and Alternate Reviewer for Manager
    • Supervisor "Select One" item's layout
    • Email communications from Leap
    • etc.
4
Public Safety Payroll ApplicationUConn Division of Public Safety
  • Meeting scheduled with Ruben Mercado for Wednesday,  to go over:
    • FD WESD
    • CoreCT Integration
5
SDLC (Documentation / Ticketing / Stash)

  • Jira
    • New ticket for Everbridge: 
    • Cancelled Jira ticket  Unable to locate Jira server for this macro. It may be due to Application Link configuration. for Avery Point Orientation form issue. Provided explanation within that ticket for this
    • Jira ticket  Unable to locate Jira server for this macro. It may be due to Application Link configuration. in Progress: 
      • The following sub-tasks were created and the work has commenced on each, starting  —
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Jira ticket  Unable to locate Jira server for this macro. It may be due to Application Link configuration. moved to Done column on Kanban board, project went live  
  • Confluence


6
Leap - General

Code Review — Mike's Application

 —  

PriorityCOVID-19 Related?ProjectFunctional StakeholderRequested ByUpdates
1(tick)EverbridgeJeremy Friedman
  • Met with Functional/IT teams
    • Discussed the potential of using Everbridge for their needs
    • Elicited requirements at a high level
2

Tax and Compliance - Foreign National Information (FNI) form

Laura House
  • Met with Laura House
    • Modified & added-to application UI per user feedback
    • Updated application code/logic in a few places
  • Completed the FNI's remaining task before promised day/time
  • Application entered the UAT stage on Sunday.
    • Up until Tuesday 9:30 AM, I did not see any forms being submitted — cannot say it's being tested rigorously
  • Happy to do a Code Review again on this project, prior to going live
3

HR - UCPEA Reclassification Form

Jessica Bowcock
  • Made progress on the couple of the tasks:
    • UConn People Search and
    • Audit logging—this one is almost complete...
    • Miscellaneous improvements w/r to code, etc.
4
Public Safety Payroll ApplicationUConn Division of Public Safety
  • Worked with Ruben on three things he brought to my attention and requested my input. We are going to circle back and resume; couldn't continue past scheduled meeting time due to other pressing tasks
5
SDLC (Documentation / Ticketing / Stash)

  • Jira 
    • Updated FNI ticket:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • For the Everbridge project
      • Created ticket  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  for working on the project
      • Created ticket  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  for the initial meeting
  • Confluence
    • Started this update page 
    • Other miscellaneous additions/updates related to documentation / inventorying






  • No labels