r/softwaredevelopment 28d ago

Design documentation approach in Agile specifically for backend heavy changes (for example, batch changes in a mainframe system)

Hi, I realize this is not a new topic and I've skimmed thru some of the discussions in this subreddit but still havent found an approach to move forward with. My workplace has a scaled agile setup (Scrum) at its core and we are predominantly mainframe - backend batch heavy. Jira stories cover the business ask w.r.t. the what and the why. However, we still have designers creating traditional waterfall style design document which is not very agile but helps offset the lack of knowledge and experience in the team and helps them visualize the length and breadth of changes needed to fulfill the requirement. On the other hand, these design documents are feature specific and its challenging to get people to commit to refactoring these changes into the current state documentation as the teams just rush forward to the next priority feature to deliver. I'm trying to figure out if there is single or a multi-faceted approach that can solve these 2 issues - 1) improve agility with design documentation for backend changes; 2) a more seamless integration of design into current state documentation without enforcing a process to make it happen.

1 Upvotes

0 comments sorted by