assignment
Running Head: Scrum 1
Scrum 4
Assignment 2
Sandeep somana
10000135035
Under guidance of: Dr. Saya Sone
Scrum
The framework to be used in this paper is discussing about an online banking system. The project is to be divided into stages and deliverables which can be accomplished independently but require other parts to be implemented together as a whole product. The division of large project into smaller projects makes it easy to design and implement the project in a team of developers. All the parts have to undergo all the stages of development from: planning, building, testing, and review independently for the framework to be executed effectively (Steadman, 2014). The order of completion of sub projects in the ultimate project is not relevant as long as they follow the guidelines required and satisfy the functional requirements of the project.
The team members developing the project require to be well informed on implementing different sub projects using design documents such as Workflow processes, UML diagrams and many more without requiring information about other parts of the system (Huether, 2012). Team members can even collaborate on achieving the same sub-task as long as they each understand their responsibilities in their respective tasks. Such sub tasks in a banking environment include: Login form, Customer Balance, and Sign up. For larger projects, each sub system can be given to a single developer to build, test and review. This can be achieved by dividing the project into sub projects which are then subdivided further until sub parts of the whole project which can be accomplished by a single individual are reached.
The product being developed requires to be defined to the highest level of granularity as possible. For example in a banking system, information such as customer name, customer contacts, customer date of birth, and any other relevant information to the product need to be collected before the project can commence production. Such information ensures that the process of planning phase of the product development begins. The provision of crucial information before the development process begins ensures that there are no details that are left behind which could cause complications further in the process. If small details such as a system requiring the customer to be able to apply a loan over a website is left out, it could result in the complete overdo of the system planning cycle. The release of sub-products of the whole product is easily manageable as it helps the management to be able to monitor the progress of the project without constantly supervising the activities of each developer. The following is a diagram of the project framework.
References
Stedman, S. (2014). Introduction to Scrum - 7 Minutes [VIDEO]. Retrieved from: https://www.youtube.com/watch?v=9TycLR0TqFA
Huether, D. (2012). Simple Cheat Sheet to Sprint Planning Meeting. Retrieved from: https://www.leadingagile.com/2012/08/simple-cheat-sheet-to-sprint-planning-meeting/