As previously mentioned in my last blog, SDLC is a popular process use by IS project teams to achieve their goals. However SDLC might not be suitable for all projects. SDLC can be at times quite complicated and sometimes may have excessive documentation causing confusion among members of a team. The relationship with their end-user members of the team may not be as strong also. This is where Agile Development becomes popular as a process for IS projects. They prefer having less documentation to avoid complicity and they like it keep objectives feasible or KISS (Keep It Simple Stupid). Their relationship with the end-user in contrast with SDLC is quite strong as they form strict contrasts and quickly develop any necessary changes for their clients.
One example of an Agile Development where team roles are seen throughout is that of Scrum development. Here are just some of its team roles.
This member represents the customer’s interest, they also represent the long and short term product vision of the product line. Their challenges include resisting the temptation to add more work, it is an agile software development system therefore it must be kept simple.
This team member leads the technical direction of the overall team. They ensure design goals such as performance, reliability, maintainability, re usability, internationalization and accessibility are met. As well as leading the design they also provide feedback
Their role is to ensure the successful completion of Work-in-progress (WIP) and to understand the process of product creation. They are responsible for motivating their team and removing bottlenecks that would slow down the team’s process. They also work closely with the architect to prove technical integrity.
This is an important role for the team. They are responsible for the actual creation of the project. They estimate the size of backlog items and translation of backlog items into engineering design and logical units of work (tasks).