2011
by Stephany Bellomo
Chief Engineer for Civil & Defense Agencies, Acquisition Support Program
This is a second in a series of posts focusing on Agile software
development. In the first post, “What is Agile?” we provided a short
overview of the key elements of the Agile approach, and we introduced
the Agile Manifesto. One of the guiding principles from the manifesto
emphasizes valuing people over developing processes. While the manifesto
clearly alludes to the fact that too much focus on process (and not
results) can be a bad thing, we introduce the notion here that the other
end of the spectrum can also be bad. This blog explores the level of
skill that is needed to develop software using Agile (do you need less
skill or more?), as well as the importance of maintaining strong
competency in a core set of software engineering processes.
Recent Comments