Don't Leave Your Architecture Behind...Kanban-Enabled Model-Driven Software Development

This presentation was created for the SATURN conference series and does not necessarily reflect the positions and views of the Software Engineering Institute.

Managing software-development-intensive projects is often a daunting task, and even with software reuse there is a high level of risk involved. To be sustainable, software products need a documented architecture, test cases written up front and updated as the project evolves, software that is written in adherence to the architecture, and software and systems tests that pass repeatedly before product release. Agile teams are forming throughout industry, as well as around Northrop Grumman, and one of the biggest challenges most Agile teams have is in managing the workload. Scrum is good, but projects often find that they are either leaving their architecture behind in order to jump into the software development feet first, or they have no idea how much they have left to do and often fail their sprints.

This presentation will cover how our projects have successfully employed Kanban to manage Agile architecture and software development.

Don't Leave Your Architecture Behind...Kanban-Enabled Model-Driven Software Development

PDF [1786 KB]

PRESENTATION

Authors

Esther Johnson

Chris Williams (Northrop Grumman)

This presentation is related to the following area(s) of work:

SATURN

Published: May 2012


SEI Blog

Find Us Here

Find us on Youtube  Find us on LinkedIn  Find us on twitter  Find us on Facebook

Share This Page

Share on Facebook  Send to your Twitter page  Save to del.ico.us  Save to LinkedIn  Digg this  Stumble this page.  Add to Technorati favorites  Save this page on your Google Home Page 

For more information

Contact Us

info@sei.cmu.edu

412-268-5800

Help us improve

Visitor feedback helps us continually improve our site.

Please tell us what you
think with this short
(< 5 minute) survey.