Add a comment

 

Re: The conflict between agile and architecture (part 1)

One of the first tasks for me is determining scope, if you have a fixed delivery, and fixed resource, then you cant have fixed scope. One of the three variables has to give. So establishment of scope even at a high level is important to establish the feasibility of delivery. On a 4 month project the feasibility of parachuting in extra resource is low, given the warm up time for a resource. Its also important that you have an active engagement with the product owner/client from the start, and that they are continuously engaged. The importance of a scope stack that is adequately prioritized is important. We use a set of standards for code construction, and once the scope has been determined the first task we normally undertake is setting up mock objects, unit testing and CI. Getting this right from the start greatly eases the flow of the project.

Re: The conflict between agile and architecture (part 1)


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).