please i need help Your team is composed of two web designers, three developers,
ID: 3595908 • Letter: P
Question
please i need help
Your team is composed of two web designers, three developers, two testers and an operations guy. You need to make sure that this big and heterogeneous team communicates smoothly and are able to work on the same project without having a lot of misunderstandings and complications. In order to do this, you have to choose a software methodology that helps them work together but separately. The client gave you a year to finish the project, but is not really aware of all the difficulties of the required task, and is still hesitant in a lot of aspects. He promised that he will be involved in all the steps of the project, and even suggested to send one of his employees to stay with you in the company until the end, which did not exactly fill you with joy. One of the team members proposed the use of the SCRUM methodology. 2. Is SCRUM appropriate for these types of requirements? Explain why or why not. (20 pts)Explanation / Answer
Yes, Scrum is the appropriate option for this requirement.
Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. In Scrum, the prescribed events are used to create regularity. All events are time-boxed events, such that every event has a maximum duration. The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules. Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage.
Roles
----------------------
Scrum master: is the person who is responsible for making the process smoothly.
The Product Owner: is the person who is responsible for improving the quality of the product and the work of the Team. Also product owner is person responsible for managing the Product Backlog, Prioritising the product backlog, ordering backlog and Provide a transparent clear backlog to the team.
Team: includes analysts, designers, developers, testers, etc. as appropriate and as relevant to the project. The scrum team works together closely, on a daily basis, to ensure the smooth flow of information and the quick resolution of issues. The scrum team delivers product iteratively and incrementally, maximizing opportunities for feedback.
Scrum - Artifacts
--------------------------------------
The Product Backlog: is a prioritized set of User Stories that describe all functionality desired for a product. This is exclusively controlled by the Product Owner
Sprint Backlog: is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.
Sprint Burn-Down Chart: The plotted point represents the sum of, The total amount of work in progress and The total amount of work that has not started yet. At any point in time in a Sprint, the total work remaining in the Sprint Backlog is visible to the entire team. The Team tracks this total work remaining for every Daily Scrum to project for achieving the Sprint Goal, the Team can manage its progress.
Release burn down: The plotted point represents the sum of, The total amount of work in progress and The total amount of work that has not started yet. This is not visible to the team. This is mainly visible to the Product owner. Product owner will get an idea about the features that is going to deliver.
Meetings
--------
Release planning: During Release Planning session(s) the Product Owner explains feature(s) to the team(s) that will be involved in their development. The team will be afforded the opportunity to ask questions of the Product Owner.
Once the team understands the feature, they should hold a design discussion and identify any spikes required.
Once the team has executed all spikes they should proceed with Vertical Slicing and Story Pointing.
Once all stories have been sliced and story pointed, a release plan will be constructed for the release
Release plan Provides a skeleton that allows Sprints to be combined into a release
Not creating tasks for each Sprint
Team will do that before each Sprint during Sprint planning
Should consist of key assumptions, including (but not limited to)
Release start
Release end date range and/or degree of confidence
Sprint length
Number of Sprints
STory point : Abstract unit of measure for estimating the relative size of a user story, feature, epic, etc.Each feature is assigned a value of x points,Usually from the Fibonacci sequence.
Sprint Planning:
Usually 1 hour per iteration week
Product Owner, Scrum Master and Team must be present
Scrum Master usually runs the meeting
Creating Sprint work items and setting sprint capacity
For each Product Backlog Items
Review the User Story and CoAs
Vet any remaining issues
Discuss complexities that may exist with the feature
Daily Planning [a.k.a. Stand-up Meetings]:
Time-boxed for 15 minutes, daily
Meetings are NOT for the Scrum Master but for the team
Meetings are NOT a status meeting they are FOR THE TEAM TO PLAN FOR THE DAY!!
Team members and SM are required to attend. POs are strongly encourage
Anyone else can attend who wants, but only the Team, PO and SM are to participate in the meeting.
User Stories
----------------
A sentence or a paragraph that describes functionality of the system from the user’s perspective.
Type of user stories
Epic: is collection of user stories. Also called compound stories.
MMF(Minimum marketable feature):Smallest set of functionalities that must be realised in order for the customer to perceive value.
Slice: A piece of MMF
Spike: A brief time boxed period to gain further understanding.
Sprint:
----------
The heart of Scrum is a Sprint, a time-box of two weeks, one week or one month during which a potentially releasable product increment is created. A new Sprint starts immediately after the conclusion of the previous Sprint. Sprints consist of the Sprint planning, daily scrums, the development work, the Sprint review, and the Sprint retrospective.
Conclusion:
-----------
Here , Scrum is appropriate. Since there is a vision about the features that is going to deliver and client will provide a person who is having a good domain knowledge, it is easy to implement scrum in this case.
There must be a product owner and a scrum master. The employee provided by the client can the product owner and he can provide the user stories. By a release planning meeting team can analyse the requirement, identify the technologies decide the feature that can be deliver for the software in the coming release. Once user stories are ready team can start release planning , define sprint size, start sprint planning and start work.
Team can have daily stand up and update their status to team discuss the complexity that they are facing. this will let team help each other and improve the productivity in a good manner.
Burn down charts also help the team to analyse the work done at any time. So team can focus on the progress of the work they are doing
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.