Time | Item | Presenter | Notes |
---|
| | | Standard Page Layouts Epic: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 13fd1930-5608-3aac-a5dd-21b934d3a4b4 |
---|
key | PAR-396 |
---|
|
Add to Paragon Figma library: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 13fd1930-5608-3aac-a5dd-21b934d3a4b4 |
---|
key | PAR-404 |
---|
|
Develop the component: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 13fd1930-5608-3aac-a5dd-21b934d3a4b4 |
---|
key | PAR-403 |
---|
|
Notes |
| | BenW | |
|
|
| Tech Lead’s capacity between Paragon and Enterprise. My primary focus is on Enterprise work and supporting the Enterprise Engineering teams. Not enough time Time constrained to create a more fleshed out technical roadmap for Paragon; most . Most of the existing, prioritized technical tasks in the backlog are in progress or have been shipped. When Raccoon Gang needs additional work and there’s not much ready to go from a design POV, I’m largely thinking of new, technical tasks in an ad hoc, as-needed manner. Without a more constant stream of work coming from design → engineering, I don’t currently have the bandwidth to brainstorm and plan impactful technical contributions to populate the technical backlog for when there isn’t as much work ready for engineering (i. Not enough Limited in time to think strategically about Paragon and do things like the Engineering from technical perspective. Ideas: Work in 2-week sprints, with design + engineering collaborating in creating a backlog for Raccoon Gang design+engineering. Supplement other folks that could help Adam, e.g. code reviews?
|
| | Marco | Product Pulse / Open edX update re: recent Paragon work |