Author Topic: Scrum  (Read 1936 times)

1202988902

  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
Re: Scrum
« Reply #30 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.

1190953011

  • Global Moderator
  • Newbie
  • *****
  • Posts: 6
Re: Scrum
« Reply #31 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.

1202988802

  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
Re: Scrum
« Reply #32 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.

1200407706

  • Global Moderator
  • Newbie
  • *****
  • Posts: 3
Re: Scrum
« Reply #33 on: August 24, 2020, 04:41:16 pm »
1. Sprint Plan Meeting
A. Identifying Sprint Goal
B. Identifying Sprint Backlog

1202408606

  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
Re: Scrum
« Reply #34 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

1200111407

  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
Re: Scrum
« Reply #35 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.

                   
 

1202908006

  • Global Moderator
  • Newbie
  • *****
  • Posts: 6
Re: Scrum
« Reply #36 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.