A long time the division between
programmers and designers (or architects) has been marked since years and for
the required job that every role needs to be implemented on a project.
It's important to distinguish again that
there are traditional methods and agile methods for a project management and
development. With this, the election and decision for choosing the right method
to create the project depends on the requirements and the time and resources
that the person/team is going to used and in terms on time the amount of
inverted time for the different phases of the project.
Now, one thing that it’s important to
consider is that every person on the project has its main role. from my point
of view a person is not able to be architect and a programmer at the same time,
you need to focus only on one thing, not because of judging or even having lack
of ability, but it's more on the sense that one person needs to focus on the
main role he or she has. Now, sometimes being all in one could be valid when
you are a small group or you are the only element of a project is taking all
the roles from a project.
Having a software strategy is important to
have a method to create the right project, normally is followed by a method
because once there is a team with specialized areas everyone needs to follow
the right process.
Normally, Agile software (like in this case
software craftsmanship) keeps quality high so the schedules should not be
affected.
For me Agile software is a good tool to
create projects this kind of methods are applied correctly when we are creating
the project for something that is not formal or even as a student it’s nice to
use it, but when we are talking about a professional and serious project the
team and specially the manager needs to take the right decision about this
Oh, and for a project the adherence is
important not only to keep the record of what we are doing but also to check
loses or incomings from the project.
Just before I finish this blog entry I would like to leave the Agile manifesto, something that could help to make a good reflection about any project where agile software development:
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Also, for more information (I used this webpage too to get more information) I recommend you to access this page to check the values and the principles.
http://www.ambysoft.com/essays/agileManifesto.html
No hay comentarios:
Publicar un comentario