---
# System prepended metadata

title: ':memo: Architecture Group Discussion'

---

# :memo: Architecture Group Discussion


### Challenges being faced? 
- How to add value to multiple streams without going into low level details (Gresh)
- Gaining enough context (Imran)
- Time splitting between concurrent streams/projects (Kader)
- Lack of subject matter experts to leverage off (Natheer)
- Certain architecture functions unclear, especially from a governance perspective (Rishay) #bringbacktheddae
- Seniors do not have enough autonomy when it comes to their streams
- Access to Nivash is a problem due to his availability and the workload he has
- Grey area around our role and  responsibilities

### What works?
- 

### What outputs do we currently produce?
- Logical Designs
- DDAE
- Given the AWS landscape, are Physical designs still required?
- Risk Assessment
- Intangible outputs such as consultation with developers, analysts, designers, SCRUM masters (takes up the most time)
    - Important to have Jira Kanban board updated so that we can see what is being worked on


### How can we improve/streamline?
- Only include a basic view of components outside of Digital (Kader)
- Revisit the AGR/DDAE pack and identify which slides are still important/necessary
- Application Portfolio Management
- Gear ourselves to work better with Vaxowave et al so that they can provide input earlier in the project life cycle, rather than having to "explain" ourselves after the fact
- Have a weekly Architecture workshop where team members can present designs and discuss ideas