SDLC & Team Architecturing based on Agile Manifesto
Posted by: doddychsaputra in Agile Manifesto, Agile for Scrum, MSF for Agile, Framework & Architecture, Enterprise development, Customization, Team Development, Design and ArchitectureHi, Geeks …See you again in my blog, in this session I would like to share about the exactly how to define the methodology for our development. I thought that these phase are become the part of a very basic designing the requirement which compulsory to initial our step. The architect and the team need to formulate the methodology based on the type of project, load project and also time line which is supposed to be discussed together with the project manager as a liaison person to the management area.I would like to walk straight ways to some little bit point which are become the main discussion in this session:
- I would like to explain and share the main core of each methodology that I’ve known as a practical person.
- Then we need to perform the team development based on the methodology that we’ve already taken.
- I would like to share as well about the probability of infrastructure that we need for accommodating your team development, in this case I am refer to use the Team Foundation server and Visual Studio Team Suite edition.
As we known before, there are many methodology for development, for instance we know about waterfall before, and then after water fall really “fall” due to this methodology following the sequential phase method which couldn’t got adaptation to the fast changing and requirement which driven by deadline and timeline such as this diagram below :
So the conclusion of the legacy failure method of waterfall are :
- Waterfall method failed to deliver the application as intended to the customer in the time frame we predicted because all of the process is sequential but the deadline could move according to the key time line that customer defined, and remember one thing that “…your customer is your king …”
- Because of the inability in us to deliver the application as the customer want then we felt like don’t have anything to ship to the hold the customer’s confidence.
- Reworking what we have may require ripping out some of what we’ve already built for instance when we are in the midst of project then suddenly there are some accidental requirement come from customer, let say 25 percent from the entire load project , but after we doing re-analyzing again then show 50 even more up to 75 percent of whole entire development supposed to be changed, oops..knock..knock…. your development team will kill you asap due to you will be charged as the most wasting time and energy in the world… J and every developer will hate you pale …
- Finally we haven’t driven the risk out of the project because integration is not complete yet and the time line will always move into the left side. and then raise new methodology based on the collaboration team with roles activities and involve the customer as the part of whole interaction role, method such as RUP (Rational Unified Process) , Agile Methodology, Agile for CMII (continuity methodology for Capability mature process)and then for short development is Agile Extreme Programming, in the other side there is a Scum methodology which based on product back log requirement designing, administering by scrum master and the sprint task as the iteration development methodology.Okay, it’s time to keen our discussion about those method above, first we should to know the essential of each method :
Currently the Collaboration team methodology has many elements which refer to agile manifesto (www.agilemanifesto.org), it was a synthesis of common beliefs that underlie the various method whether contain such elements like this :
- Individuals and interactions over process and tools (TDD, Source control and work item traceability)
- Working software over comprehensive documentation (process guidance)
- Customer collaboration over contract negotiation (Timeline management and resources )
- Responding to change over following plan (Iteration process drive the project goal )
So, The modern tools of team collaboration development will refer to the Agile Manifesto principle, in next session i will describe one by one of each methodology of SDLC refer to Agile Manifesto.
Cheers,
Doddy Ch Saputra, MCPD,MCITP,MCTS

Entries (RSS)