COEPD Forum

Business Analyst => Business Analyst Concepts Discussion => Topic started by: Bhanu Teja Nukala on August 24, 2018, 02:26:02 am

Title: Scrum
Post by: Bhanu Teja Nukala on August 24, 2018, 02:26:02 am
What are the roles in Scrum?
Title: Re: Scrum
Post by: kalyan ram.N on August 24, 2018, 02:41:47 am
Three essential roles for scrum success. A scrum team has a slightly different composition than a traditional waterfall project, with three specific roles: product owner, scrum master, and the development team.
Title: Re: Scrum
Post by: 1181279905 on August 27, 2018, 07:34:25 pm
In scrum based projects there are mainly three roles: product owner, scrum master and development team. scrum doesn't need a project manager.
Title: Re: Scrum
Post by: 1182459701 on September 27, 2018, 04:09:44 pm
Scrum has three roles:
1)product owner: has the vision of the product and the projects key stakeholder.
2)scrum master:Helps the team build the product by conducting meetings, removing impediments and working with product owners.
3)development team: builds and develops the product
Title: Re: Scrum
Post by: 1181278605 on October 25, 2018, 10:54:35 am
SCRUM has three roles=

1.product owner= he will decide what need to be in the product and he will responsible for how the product has to be. BA can play the role as a product owner.

2. scrum master= he will be the monitor of the project. he mainly look after the project performance. if any issue raised by the team his role is to bring the solution for them.

3. development team= build and developed the software. they take decision on which sprint need to deliver and time frame.

in agile we didn't need any project manager.
Title: Re: Scrum
Post by: 1180810109 on November 01, 2018, 01:50:31 pm
The most important three roles of Scrum are

1)Product Owner
2)Scrum Master
3)Development Team

These three roles are coequal and all of them have certain responsibilities.

1)Product Owner :

Product Owner will decide what needs to be in the product  and will be responsible for how the product has to be.

2)Scrum master :

He will monitor the performance of the team within the sprint .Team will raise all their issues to scrum master and he will run to look for  answers .This role can be played by any person in team normally BA s play this role

3)Development Team :
 
Different from other methods, in Scrum a team is not just the executive organ that receives its tasks from the project leader, it rather decides self dependent, which requirements or User Stories it can accomplish in one sprint. It constructs the tasks and is responsible for the permutation of those – the team becomes a manager. This new self-conception of the team and the therewith aligned tasks and responsibilities necessarily change the role of the team leader/project leader. The Scrum Master does not need to delegate all the work and to plan the project, he rather takes care that the team meets all conditions in order to reach the self-made goals.
Title: Re: Scrum
Post by: 1180108809 on November 05, 2018, 04:21:46 pm
Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

Scrum itself is a simple framework for effective team collaboration on complex products.  Scrum co-creators Ken Schwaber and Jeff Sutherland have written The Scrum Guide to explain Scrum clearly and succinctly.  This Guide contains the definition of Scrum. This definition consists of Scrum’s roles, events, artifacts, and the rules that bind them together.

Scrum is:

Lightweight
Simple to understand
Difficult to master
Title: Re: Scrum
Post by: 1182198007 on December 04, 2018, 11:52:42 pm
The scrum roles are basically divided into two broad categories, Core Roles and Non-core Roles.
Core Roles

Core roles are those roles which are mandatorily required for producing the project’s product or service. Individuals who are assigned core roles are fully committed to the project and are ultimately responsible for the success of each project iteration and of the project as a whole.

Non-core Roles

Non-core roles are those roles which are not mandatorily required for the Scrum project and may include team members who are interested in the project. They have no formal role in the project team and may interface with the team, but may not be responsible for the success of the project. The non-core roles should be taken into account in any Scrum project.

Core roles include:

The Product Owner

The Product Owner is the person responsible for achieving maximum business value for the project. He or she is also responsible for articulating customer requirements and maintaining business justification for the project. The Product Owner represents the Voice of the Customer.

The Scrum Master

The Scrum Master is a facilitator who ensures that the Scrum Team is provided with an environment conducive to complete the project successfully. The Scrum Master guides, facilitates, and teaches Scrum practices to everyone involved in the project; clears impediments for the team; and, ensures that Scrum processes are being followed.

The Scrum Team

The Scrum Team is the group or team of people who are responsible for understanding the requirements specified by the Product Owner and creating the Deliverables of the project.

 

Non-core roles include:

Stakeholder(s)

Stakeholder(s) is a collective term that includes customers, users, and sponsors, frequently interface with the Scrum Core Team, and influence the project throughout the project’s development. Most importantly, it is for the stakeholders that the project produces the collaborative benefits.

Scrum Guidance Body (SGB)

It is an optional role, which generally consists of a set of documents and/or a group of experts who are typically involved with defining objectives related to quality, government regulations, security, and other key organizational parameters. This SGB guides the work carried out by the Product Owner, Scrum Master, and Scrum Team.

Vendors

Vendors include external individuals or organizations, provide products and/or services that are not within the core competencies of the project organization.

Chief Product Owner

Chief Product Owner is a role in bigger projects with multiple Scrum Teams. This role is responsible for facilitating the work of multiple Product Owners, and maintaining business justification for the larger project.

Chief Scrum Master

Chief Scrum Master is responsible to coordinate Scrum-related activities in large projects which may require multiple Scrum Teams to work in parallel.
Title: Re: Scrum
Post by: 1181059202 on December 11, 2018, 10:23:29 pm
Three roles - scrum master, scrum product owner and scrum team. Each of these roles has a defined set of responsibilities.
Title: Re: Scrum
Post by: 1182916109 on December 14, 2018, 01:08:08 pm
Scrum: Scrum is a subset of Agile. It is a lightweight process framework for agile development, and the most widely-used one.

A “process framework” is a particular set of practices that must be followed in order for a process to be consistent with the framework. For example, the Scrum process framework requires the use of development cycles called Sprints, the XP framework requires pair programming.
“Lightweight” means that the overhead of the process is kept as small as possible, to maximize the amount of productive time available for getting useful work done.
A Scrum process is distinguished from other agile processes by specific concepts and practices, divided into the three categories of Roles, Artifacts, and Time Boxes. These and other terms used in Scrum are defined below. Scrum is most often used to manage complex software and product development, using iterative and incremental practices. Scrum significantly increases productivity and reduces time to benefits relative to classic “waterfall” processes. Scrum processes enable organizations to adjust smoothly to rapidly-changing requirements, and produce a product that meets evolving business goals. An agile Scrum process benefits the organization by helping it to
1. Increase the quality of the deliverable
2. Cope better with change
3. Provide better estimates while spending less time creating them
4. Be more in control of the project schedule and state
Title: Re: Scrum
Post by: Adithya Mahendra on February 25, 2019, 10:29:55 am
SCRUM team consists of roughly about 10 members that is, 1 product owner, 1 scrum master and about 7-8 developers. This is the core SCRUM team, whereas during the requirements gathering stage, the external stakeholders shall also take part.
Title: Re: Scrum
Post by: 1191940101 on March 23, 2019, 09:09:49 am
 What is the BA role in Scrum?
Title: Re: Scrum
Post by: 1191940001 on March 30, 2019, 02:53:59 pm
 What are the qualities of a good scrum master ?
Title: Re: Scrum
Post by: 1171835509 on April 03, 2019, 04:56:49 pm
How are sprints in scrum categorized?
Title: Re: Scrum
Post by: 1182234512 on April 10, 2019, 08:45:34 pm
The most important three roles of Scrum are:

1. Product Owner
2. Scrum Master
3. Development Team
Title: Re: Scrum
Post by: Jayanth mangu on April 21, 2019, 03:41:57 pm
Many people say that using scrum is quite risky process. How can we complete the process without any errors? are there any bullet points to be noted before using scrum
Title: Re: Scrum
Post by: 1192767805 on August 03, 2019, 10:27:28 am
what is the average scrum team size?
Title: Re: Scrum
Post by: 1190244102 on August 03, 2019, 07:59:29 pm
Scrum has three roles:
1)product owner: has the vision of the product and the projects key stakeholder.
2)scrum master:Helps the team build the product by conducting meetings, removing impediments and working with product owners.
3)development team: builds and develops the product
Title: Re: Scrum
Post by: 1190763804 on August 27, 2019, 07:48:09 pm
         Scrum is an Iterative development methodology used to manage Software projects. In Scrum based projects, there is not a specific project manager directing project team tasks, the team is self-directed with co-located team members relying on communication over documentation for effective project delivery.

   There will be a Scrum Team, comprised of BAs, Developers, and Testers. Each Team size will on average be 7-8. Product Owner will decide what needs to be in the product and will be responsible for how the product has to be. He will regularly interact with Customers and BAs. The Scrum Master will monitor the performance of the team within the Sprint.

   Product burn down shows how much work was left to do at the beginning of each Sprint. Sprint is the Period that Team decides to deliver their objectives. Normally a Sprint period will be for 2 weeks to 4 weeks.

   There are some Meetings will be held on as Sprint Planning Meeting, Daily Scrum Meeting, Sprint Review Meeting and Sprint Retrospective Meeting.
Title: Re: Scrum
Post by: 1191403409 on October 13, 2019, 07:35:29 pm
The scrum master is the role responsible for gluing everything together and ensuring that scrum is being done well. In practical terms, that means they help the product owner define value, the development team deliver the value, and the scrum team to get to get better.
Title: Re: Scrum
Post by: 1191649002 on October 23, 2019, 05:10:32 pm
Where does a Business Analyst fit into this Scrum Framework ?
Will he (BA) be doing a supportive role like assisting the PO in maintaining and prioritizing the requirements ? 
Title: Re: Scrum
Post by: 1190686707 on December 14, 2019, 11:53:18 am
Scrum has three roles:
1)product owner: has the vision of the product and the projects key stakeholder.
2)scrum master:Helps the team build the product by conducting meetings, removing impediments and working with product owners.
3)development team: builds and develops the product
Title: Re: Scrum
Post by: 1190953311 on December 16, 2019, 07:00:51 pm
1. what do you know about impediments in scrum?

2. what is velocity?

3. what is the build-breaker?
Title: Re: Scrum
Post by: 1190956211 on December 28, 2019, 12:08:46 pm
Agile is a Software Development methodology under which scrum falls. Scrum is a frame work most widely used in the agile model. Scrum consists of 3 roles.
1. Product owner:Holds the vision for the product

2. Scrum Master:Helps the team to follow scrum best practices and guides the development team.

3. Development: The team who is responsible to Build the product/project.
Title: Re: Scrum
Post by: 1181698407 on March 30, 2020, 07:07:17 pm
Scrum is an agile process framework for managing complex knowledge work, with an initial emphasis on software development, although it has been used in other fields and is slowly starting to be explored for other complex work, research and advanced technologies.
Title: Re: Scrum
Post by: 1200182002 on April 11, 2020, 02:25:11 pm
In Scrum, there are three roles: Product Owner, Development Team, and Scrum Master. Together these are known as the Scrum Team

Scrum Master: Roles and Responsibilities
The Scrum Master helps the product group learn and apply Scrum to achieve business value. The Scrum Master does whatever is in their power to help the Team, Product Owner and organization be successful. The Scrum Master is not the manager of the Team members, nor are they a project manager, team lead, or team representative. Instead, the Scrum Master serves the Team; he or she helps to remove impediments, protects the Team from outside interference, and helps the Team to adopt Agile development practices. He or she educates, coaches and guides the Product Owner, Team and the rest of the organization in the skillful use of Scrum.
Scrum Master ensures everyone follows the practices prescribed by Scrum.

A Scrum Master is a facilitator and Servant Leader who encourages and demands self-organization from the development team.
A Scrum Master enables close cooperation across all roles and functions, addresses resource issue and disobedience of scrum practices.
A Scrum Master protects the team from external and internal distractions.
A Scrum Master removes impediments so the team can focus on the work at hand and follow scrum practices.
A Scrum Master is not typically a manager or lead, but he is an influential leader and coach who does not do direct command and control.

Scrum Product Owner: Roles and Responsibilities
The Product Owner is responsible for maximizing return on investment (ROI) by identifying product features, translating these into a prioritized list, deciding which should be at the top of the list for the next Sprint, and continually re-prioritizing and refining the list. The Product Owner has profit and loss responsibility for the product, assuming it is a commercial product. Product Owner in Agile is like a spokesperson for customer and needs to represent them,

A Product Owner owns the Product backlog and writes user stories and acceptance criteria.
A Product Owner is responsible for prioritizing the Product Backlog is prioritized and decides the release date and the content.
A Product Owner accepts or rejects product backlog item.
A Product Owner has the power to cancel the Sprint, if he thinks the Sprint goal is redundant.
A Product Owner is the one who is responsible for the Return on Investment (ROI) of the product.


Development team: Roles and Responsibilities
A Development Team is a collection of individuals working together to develop and deliver the requested and committed product increments. It comprises of cross-functional members who are capable of achieving the sprint goals. This could include software engineers, architects, programmers, analysts, system admins, QA experts, testers, UI designers, etc.

The Development Team builds the product that the Product Owner indicates: the application or website, for example. The Team in Scrum is “cross-functional”
The Development Team includes all the expertise necessary to deliver the potentially shippable product each Sprint
The Development Team is self-organizing, with a very high degree of autonomy and accountability.
The Development Team decides how many items to build in a Sprint, and how best to accomplish that goal.
The Development Team is a cross functional, small and self-organizing team which owns the collective responsibility of developing, testing and releasing the Product increment.
The Development Team may not appoint any team lead since decisions are taken collectively by the team.
Title: Re: Scrum
Post by: 1190952411 on May 15, 2020, 06:12:14 pm
What is Scrum?
Scrum methodology is an iterative process of the agile approach that focuses on delivering value in the shortest amount of time. When using the scrum approach, the project is broken down into smaller builds, called sprints, with specific time frames.
Sprints generally last one to two weeks and involve daily meetings to discuss progress and development. Once a sprint is complete, the team gets together again to discuss how to approach the next sprint.

The roles, responsibilities, and meetings are fixed in a Scrum. In each sprint, there is sprint planning, daily stand-up, sprint demo and sprint retrospective. There are task boards and burn down charts to follow up on the progress of the sprint as well as to receive incremental feedback.

Roles in a scrum:
1.   Product Owner
2.   Scrum Master
3.   Scrum Team

Steps in the Scrum flow:
1.   Product backlog
2.   Sprint planning
3.   Backlog refinement
4.   Daily Scrum
5.   Sprint review meeting
6.   Sprint retrospective meeting
Title: Re: Scrum
Post by: 1192168812 on May 29, 2020, 12:38:42 pm
Scrum: Scrum is a subset of Agile. It is a lightweight process framework for agile development and the most widely-used one.

A “process framework” is a particular set of practices that must be followed in order for a process to be consistent with the framework. For example, the Scrum process framework requires the use of development cycles called Sprints, the XP framework requires pair programming.
“Lightweight” means that the overhead of the process is kept as small as possible, to maximize the amount of productive time available for getting useful work done.
A Scrum process is distinguished from other agile processes by specific concepts and practices, divided into the three categories of Roles, Artifacts, and Time Boxes. These and other terms used in Scrum are defined below. Scrum is most often used to manage complex software and product development, using iterative and incremental practices. Scrum significantly increases productivity and reduces time to benefits relative to classic “waterfall” processes. Scrum processes enable organizations to adjust smoothly to rapidly-changing requirements and produce a product that meets evolving business goals. An agile Scrum process benefits the organization by helping it to
1. Increase the quality of the deliverable
2. Cope better with change
3. Provide better estimates while spending less time creating them
4. Be more in control of the project schedule and state
Title: Re: Scrum
Post by: 1202990202 on May 30, 2020, 11:12:19 am
Scrum team refers to the team that is present in the Agile methodology
Title: Re: Scrum
Post by: 1192091407 on June 05, 2020, 05:55:31 pm
Difference between Sprint Review Meeting and Sprint Retrospective Meeting?
Title: Re: Scrum
Post by: 1202988902 on June 18, 2020, 03:27:50 pm
A Highly Effective Scrum Master:
1. Focuses the team on the goals of the current iteration, keeping them on track: Having a short window in which to deliver working software helps keep the team focused, but should that not be sufficient, the Scrum Master is there to help by keeping the goals visible on a prominent score board, keeping the daily standup meeting focused on goals, and removing distractions that would otherwise interfere with reaching goals.

2. Removes barriers that block the team so they can deliver high quality working software: The Scrum Master monitors such distractions as too many meetings, unneeded procedural complexity, resource-based delays, or work environment or human factor challenges, and protects the team from them all.

3. Works with the Product Owner, providing a check and balance between getting more done and maintaining high quality and efficiency: The Product Owner is rightfully concerned with receiving the most visible value. The Scrum Master makes sure that this is done, but not at the expense of software quality.

4. Coaches the team in Scrum project management practices through:

Building Organic, self-organizing agile teams and integrating them into the enterprise
Creating a guiding, shared team vision, project vision, and product vision
Implementing simple, adaptable methodology rules to deliver business value rapidly and reliably
Creating open flow and exchange of information among project team members and external groups
Maintaining a light touch by supporting team autonomy, flexibility and customer value focus without sacrificing control
Tracking and monitoring the project for timely and relevant feedback while instituting systemic learning and adaptation
5. Introduces selected engineering practices and tools to help ensure that each iteration is potentially shippable, including any or all from the following list:

Automated Builds and Continuous Integration: Reduce time and effort associated with manual builds and the risk of big-bang integrations
Simple Design and Refactoring: Keep incremental development from leading to poor architectures
Multi-Level/Automated Testing and Test-Driven Development: Reduce testing time and effort and allow developers to make changes with confidence
Pair Programming: Increase software quality without impacting time to deliver
Other: Industry best practices, standard corporate practices, and procedures which may benefit the project
6. Encourages collaboration and facilitates Scrum-prescribed collaborations through:

Release Planning Sessions: To determine what a Release should include and when it should be delivered
Iteration Planning Sessions: Elaborate, estimate and prioritize highest-value product deliverables for the next iteration
Daily Standup Meetings: Very brief meetings to rapidly take the pulse of the project, address challenges, and coordinate activities of the team and with the Product Owner
Iteration Review / Demo Sessions: Demonstrate completed functionality to interested stakeholders and users to show      progress and gain important feedback
Iteration Retrospective Sessions: Reflect on project and process issues and take action as appropriate. Continuous collaboration and process improvement
As you can see, a Scrum Master has many hats to wear, some in addition to those usually associated with project management.  Agile emphasizes people over process, and that is certainly evident in the team-directed focus of a Scrum Master. Agile emphasizes delivering customer value over extensive documentation and other non-value added artifacts and processes, and that is reflected in the Scrum Master?s emphasis on engineering practices and focus on delivering working value-driven software. Agile and Scrum promote open communication and active contributions from team members and the Product Owner throughout the project, and a highly effective Scrum Master accomplishes this by encouraging and facilitating on-going verbal collaboration, both formally and informally, and by promoting the use of prominent visual displays of project status. A Scrum Master who executes on the strategies outlined here will indeed be a highly effective Scrum Master, and will truly meet or exceed the customer?s expectation of value.
Title: Re: Scrum
Post by: 1190953011 on July 17, 2020, 12:48:05 pm
The term ?Scrum? was first coined by Hirotaka and Ikujiro in the year 1986 in a newspaper.
Scrum is a framework comprising of iterative(sprint) process or methodology to achieve an ultimate goal. It can be implemented when the project is lagging behind or at the starting of the Project. In Scrum methodology, the team is self-directed who relies on documentation and co-team members for successful and efficient delivery of project.
Title: Re: Scrum
Post by: 1202988802 on August 18, 2020, 05:36:50 pm
The Roles in SCRUM are

1. Product Owner: He gets requirement from business/users and communicate the same to BA.
2. SCRUM Master: He monitors the performance of the team. BA or developer can act as a SCRUM Master.
3. BA: He acts as a bridge between PO , developer and tester.
4. Developer: He develops the code as per the acceptance criteria given by BA.
5. Tester: Once the developer develops the code for the model he test the test cases as approved by the BA.
Title: Re: Scrum
Post by: 1200407706 on August 24, 2020, 04:41:16 pm
1. Sprint Plan Meeting
A. Identifying Sprint Goal
B. Identifying Sprint Backlog
Title: Re: Scrum
Post by: 1202408606 on September 07, 2020, 08:57:50 pm
scrum is a development methodology used to manage the software projects. the team is self directed the major roles of scum are
1.scrum team
2.product owner
3. scrum master
Title: Re: Scrum
Post by: 1200111407 on September 16, 2020, 02:25:50 pm
In scrum, product vision is important (Single line high level statement).
It includes :
                   Product Vision
                   Epic
                   Modules
                   User story
                   Tasks and Sub-tasks
The most important function of scrum and the reason to use it is "Product Backlog Refinement" which takes the 10% of sprint time for the next user stories so that dev team will be ready for the future user stories.
SCRUM has three roles=

1.product owner= he will decide what need to be in the product and he will responsible for how the product has to be. BA can play the role as a product owner.

2. scrum master= he will be the monitor of the project. he mainly look after the project performance. if any issue raised by the team his role is to bring the solution for them.

3. development team= build and developed the software. they take decision on which sprint need to deliver and time frame.

in agile we didn't need any project manager.

                   
 
Title: Re: Scrum
Post by: 1202908006 on September 19, 2020, 01:27:19 pm
Roles of Scrum:

1)   Scrum Master.
2)    Product Owner.
3)   Development Team (Scrum Team) (or) Tech Team.

1)   Scrum master:

The scrum master be responsible for monitoring the performance of the team. The tech team will raise all their issues to scrum master and he will be responsible to run through their queries. Generally this role is played by any person in team or normally Business Analyst will play this role.

2)   Product Owner:

Product Owner will decide what should be included in the product and he will be responsible that how the product should look like. The product owner will be responsible for the product design.

3)   Development Team:
 
Development team will be responsible for developing the product and deliver to their responsible end user. They receive their tasks from the project leader, Business analyst and they develop their product according to their received requirement. The Scrum Master does not need to delegate all the work and to plan the project, he rather takes care that the team meets all conditions in order to reach the self-made goals.