Another Way to Burn This article describes a burndown chart based upon test cases rather than eﬀort and describes its advantages. It is intended for readers already familiar with the concept of a burndown chart.

First Page		Document Content
Date: 2015-12-07 19:50:12 Software testing Software development Project management Software engineering Business Agile software development Management Software development process Earned value management Burn down chart Test-driven development Test case		Another Way to Burn This article describes a burndown chart based upon test cases rather than eﬀort and describes its advantages. It is intended for readers already familiar with the concept of a burndown chart. Add to Reading List Source URL: www.sasqag.org Download Document from Source Website File Size: 56,57 KB Share Document on Facebook

	Checking Consistency of Real-Time Requirements on Distributed Automotive Control Software Early in the Development Process using UPPAAL Jan Toennemann1 , Andreas Rausch1 , Falk Howar2 , and Benjamin Cool3 1 DocID: 1xU0r - View Document
	An Architecture-Centric Process for MILS Development Julien Delange, Min-Young Nam, Peter Feiler, and Will Klieber Carnegie Mellon Software Engineering Institute 4500 Fifth Avenue Pittsburgh, PA, USA DocID: 1vnSo - View Document
	Design Thinking for Agile Development Teams Why Design Thinking? The Agile Development Process is mostly focused on the speed and quality of software development. This is due to increasing and fast changing customer dema DocID: 1tMRY - View Document
	Design Thinking for Agile Development Teams Why Design Thinking? The Agile Development Process is mostly focused on the speed and quality of software development. This is due to increasing and fast changing customer dema DocID: 1tGgP - View Document
	Revolutionising the process of software development Justyna Petke Centre for Research in Evolution, Search and Testing University College London DocID: 1tDnN - View Document