Message from discussion Breaking complex features into something that can be delivered in an iteration

Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Received: by 10.100.253.5 with SMTP id a5mr89297ani.21.1224093623654; Wed, 15 
	Oct 2008 11:00:23 -0700 (PDT)
Date: Wed, 15 Oct 2008 11:00:23 -0700 (PDT)
X-IP: 62.190.48.222
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; 
	InfoPath.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; 
	.NET CLR 3.5.21022),gzip(gfe),gzip(gfe)
Message-ID: <4b61da32-758c-4939-8695-ac2f07b1a8df@v13g2000pro.googlegroups.com>
Subject: Breaking complex features into something that can be delivered in an 
	iteration
From: Stevio <st...@jsbrewer.plus.com>
To: All About Agile <allaboutagile@googlegroups.com>

Q1. Is there any very clear and concise presentation/material
available anywhere which summaries to senior software chaps how to
break complex features down into chunks that are small enough to
implement and test within a single Scrum iteration?

Q2. If a new feature requires a major investment in terms of new
architectural infrastructure which is going to take multiple sprints
to develop (it's 3 months work), what do you deliver as working,
tested code at the end of an sprint? If you spend lots of time
developing unit tests for this, they are pretty much useless later in
the process once more of the design has been implemented and are
therefore seen as wasted effort.

Q3. Does anyone know of a real world example that is well documented
somewhere which shows the power of Agile in a complex embedded
development environment (not applications)?

Both of the above are being given as objections to us adopting Scrum
and I'd like some help removing these blockages.

Thanks for any suggestions,
Stevio