As a PM I need a 3-page paper on why Scrum is fun

Consistency eventually beats intensity [ CITATION Bha20 \l 1033 ]. I believe the only way to

stay consistent is to thoroughly enjoy what you are doing and there must be a daily dosage or an

element of fun to make the whole process easier. The classic phrase from Sutherland and

Schwaber is: Scrum is simple, but Scrum is hard [ CITATION Joe13 \l 1033 ]. Apart from a

dysfunctional personal chemistry, with any decent team, scrum is, at most times, fun. Following

are some good reasons to work with Scrum [ CITATION Agi20 \l 1033 ]:

1. Competitiveness

In order to tackle the fast change in market trends, the team that shows flexibility and

contemporary reaction to time and market thereby staying competitive results in

developing a creative competitive advantage for themselves.

2. Confidence through transparency

During the execution of various levels in Sprint, transparency plays a vital role. The

reason why Scrum is so efficient is due to the transparency maintained during stakeholder

engagement where they are informed where the project stands in terms of progress

resulting in identifying the weaknesses and effective teamwork.

3. Build Quality in

In Scrum, at every sprint, testing is considered to be an integrative component i.e., the

software is tested and documented as ‘ready’ only after the testing is completed. In order

to secure the quality of every aspect from the beginning, Continuous Integration methods

are suitable and appreciated.

 4. To have costs under control

Though the efforts and complexity involved in a project is rough, the duration is fixed.

Certain factors such as customer involvement, allowing changes, and maintaining

transparency result in a precise cost accounting throughout the project.

5. Recognize risks in time- systematic risk management

In Scrum, problems and bugs are identified at a faster pace due to the regular releases

resulting in on time reaction and resolution of those issues and problem. There are long-

term statements about time factor and product completion possible because of factors as

team velocity [ CITATION Agi20 \l 1033 ].

As we know, the nature of a new product development is a rather stressful business as it must be

built quickly and on time as per the customer demands and expectations. This ‘Stress’ is

continual throughout the development process i.e., the whole team is faced with the business

problem of delivering something efficient and useful in the given timeline, unlike the old

waterfall method where the stress is controlled. With Scrum, the teams are supposed to have

‘positive’ stress thereby eliminating ‘bad’ stress along the way. Having said that, the

fundamental pressure involved in product development business is inevitable.

In Scrum, the development behind any skill feels endless but takes years of hard work and

practice to become a true professional. For some people, this idea seems to be discomforting. But

this idea of scrum being hard, or discomforting is mainly inside the heads of people. Scrum

welcomes changes with open arms i.e., changes can be identified in the on-going sprint and

reported to the Product Owner resulting in customer satisfaction. The idea presented or

demanded by the customer is fulfilled by the team as a whole by effective communication,

collaboration, respect along with mutual understanding in developing the product.

In complex environments, Scrum cannot predict the future [ CITATION Wil19 \l 1033 ]. As

scrum is founded on empiricism (transparency, inspection, adaptation), it exits to take one step

by assessing it and then eventually adapting to the given environment. After making the

Definition of Done clear to everyone onboard (Development Team, Product owner, and key

stakeholders), discussion on what to do in the next increment is conducted ensuring each team

member is on the same page. Unlike other frameworks, Scrum allows only a limited number of

people to determine what needs to be done. This means that the Development Team is held

accountable for maintaining the Product Backlog.

In summary, the core idea of implementing Scrum lies in collaborative functioning and making

decisions as a team [CITATION Agi20 \l 1033 ]. Software development is all about being

creative and working efficiently when taken responsibilities of the multi-sided activities.

References
Ageling, W.-J. (2019, September 18). 11 reasons why Scrum is great for developers. Retrieved

from Serious Scrum : https://medium.com/serious-scrum/11-reasons-why-scrum-is-great-

for-developers-dd4830cccaad

Agile42. (2020, December 4). Scrum Hit list – 10 good reasons for Scrum. Retrieved from

https://www.agile42.com/en/agile-info-center/scrum/10-good-reasons-implement-scrum/

Little, J. (2013, September 7). Scrum is Hard! (Scrum is Fun!). Retrieved from 101 Ways:

https://www.101ways.com/2013/09/07/scrum-is-hard-scrum-is-fun/

Srinivasan, B. (2020, July 22). Are you having Fun? . Retrieved from Scrum.org:

https://www.scrum.org/resources/blog/are-you-having-fun