Abstract
AbstractTraditional Systems Engineering artifacts and terminology have a negative connotation in some companies and industries that use Agile development. This paper aims to show that the terms and concepts typically associated with traditional systems engineering are not scary for Agile software development. They can, and should, be tailored and utilized during the Agile development process. Many times, terminology and lack of understanding lead to Agile practitioners shying away from what are considered traditional Systems Engineering artifacts such as requirements, architectures designs, documented interfaces, verification, gate reviews, etc. Agile actually already employs many of these artifacts and concepts but simply uses a different terminology when referring to them.This paper helps advance the mindset that traditional Systems Engineering terms, concepts, and artifacts are not something to avoid in Agile by providing alternative ways to describe and think about them in an Agile setting.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
