Architectural deliverables

Last post 05:48 pm September 25, 2019 by Krishna Chaitanya Sunkavalli

No replies yet

05:48 pm September 25, 2019

Hi,

I'm a solution architect responsible for designing the solution architecture and deliver required artifacts like Infrastructure Diagrams, Application Integration models, overall solution models.

Can these deliverables be treated as user stories? If yes, some of these deliverables might extend beyond a sprint and may end up impacting team's velocity numbers. Or is it advisable to track these deliverables in a separate work board using Kanban instead of adding them to the main product backlog?

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.