Large enterprises face three challenges: to innovate and act as a start-up, to use a budgeting process that keeps the organization’s strategy in touch with changing market conditions, and to transform the whole IT department to agile. Principal analyst Michael Azoff explains Ovum’s view on creating an agile enterprise.
Historical data is a key resource for judging the effectiveness of software process improvement methods and also for calibrating software estimation accuracy. In this article, Capers Jones compares Agile and Scrum with a sample of contemporary software development methods using several standard metrics.
Suzanne and James Robertson have released the 3rd edition of their book Mastering the Requirements Process. This edition includes material focused on the challenges of requirements in modern project environments, including agile and outsourcing relationships.
"Enterprise Software Delivery" is the latest book by Alan W. Brown, and is a must-read guide for anybody concerned with the development and delivery of software in a large organisation.
The Defense Industry is often viewed as a very “non-Agile” culture. But even in this environment, you can successfully apply Agile principles and practices and tailor them to fit your needs.
Laila Lotfi explains how using automated error reporting results in greater customer trust, higher renewal rates, lower maintenance costs, and fewer opportunities for the competition. 2
Dr Rebecca Parsons is the Chief Technology Officer for ThoughtWorks, and a Director of the Agile Alliance. She discusses the trends in database technology, continuous design & delivery and Agile.
Certified Scrum Master training tells us we must conduct Reviews (aka Demo's) at the end of every Sprint. Rarely do we get guidance on how to have a great Sprint Review. 5
Project Charters have rightfully focused on scope & goals. The Agile Development Team Charter reviews the Agile Prime Directive, Incremental Innovation Statements, and Team Member User Stories. 2
One of the main challenges when designing software architecture is considering quality attributes. Not only their design turns out to be difficult, but also the specification of these attributes. 2
Gojko Adzic has written Specification by Example in which he provides advice and guidelines on adopting this approach as a way to create living documentation on a software development project. 7
Active Architecture is a type of documentation that is based on User Stories and helps to bridge the gap between User Stories in Agile Projects and large design deliverables on Traditional projects. 14