Active Directory, AS/400, Business Intelligence, CIO, Cisco, Database, DataCenter, Desktops, Development, DNS, Exchange, Exchange 2003, Exchange 2007, Hardware, iSeries, Linux, Lotus Domino, Lotus Notes, Management, Marketing Technology, Microsoft Access, Microsoft Excel, Microsoft Windows, Mobile, Networking, Oracle, OS, Outlook, Outlook 2003, Outlook 2007, Routers, RPG, RPGLE, SAP, Security, Servers, SQL, SQL Server, SQL Server 2005, Storage, Tech support, Virtualization, Visual Basic, VoIP, VPN, Windows 7, Windows Server, Windows Server 2003, Windows Server 2008, Windows XP VIEW ALL TAGS
Considering a sprint of 4 weeks, the development team completes their development in the first 3 weeks . The testing team starts testing immediately after that for the last one week. What does the development team do during that period. Do they start the next sprint??
What happens if the development phase slips (takes more time than estimated) and as a result it eats up the testing time? What do we do? Do we add the testing activities to the next sprint?
When do we start the planning of the next sprint? Is it at the end of the previous sprint or before one ends that the next one can be planned?