Venkatesh Rajamani

No matter what the future brings, building a capable and resilient organisation is the need of the hour. At tryScrum, our mission is to help organisations become capable and resilient. In this blog, I will share my experience of some of the tenets that helped organisations I worked with. This model aims to show you what to strive for and how to get started to become a high-performing organisation.

Though, there is no universal definition of what is an Agile Coach. I want to define, Someone who developed deep expertise to help people, teams, and organisations enable better customer outcomes by focusing on an organisation’s internal and external orientation.

The Sprint Review is an integral event in Scrum as it gives the platform to Scrum Team to showcase the product to stakeholders and invite feedback from them. But often find the seats with the shareholder’s name on them empty.

In tis blog post, Professional Scrum Trainer Venkatesh Rajamani walks through challenges Scrum Masters face and how to resolve them.

The most perceptible activity that can take place in Scrum is the Sprint Review. The feedback-driven working session enables the demonstration of the functionality built during the Sprint to get feedback from the Stakeholders. In the following article, we will discuss the aspects of Sprint Review.

Can you be Agile with fixed-bid Projects? It can be a challenging leadership problem and problematic to resolve. However, there is no direct and clear answer to the query. For clearing the dilemma, I have to recall the elementary difference between a project mindset and a product mindset.

In this blog, I will share my valuable experience in my journey toward becoming a Scrum Master. I would also share stories of various professionals, including women, who successfully got a Scrum Master’s job even after a career break. 

In this blog, Venkatesh Rajamani shares tips on being a good Scrum Master.

Myth 1 – Scrum is a Methodology To bust this first myth, I would prefer to differentiate between the concepts of methodology and framework. Methodology vs. Framework A specific methodology is a well-defined set of principles, concepts, tools, and associated practices that guide processes to meet a focused goal. The methodology is fundamentally more prescriptive. On the other hand, a framework is a flexible yet incomplete structure that leaves space for different practices and related tools requisite for the overall process. Thus, a framework is, practically, less prescriptive. Source: wiki People often refer to Scrum as Methodology. From a practical point of view, Scrum is not a methodology, neither by definition. Instead, Scrum focuses on the scientific implementation of empiricism. As a result, it strikes the chord between well-defined principles and associated practices in a balanced manner. Self-Managing teams and their dedicated, collective intelligence form the basis of Scrum. The teams solve varieties of complex problems through a series of adaptive solutions. Myth 2 – Agile is equivalent to Scrum 50% of people I interact with use Agile and Scrum interchangeably. When they say something like 'We are performing or doing Agile', they mean they are doing Scrum. On a practical note, these two things are not the same. Scrum is invariably a technical, lightweight framework. It strategically helps teams and organisations generate value via adaptive solutions suitable for solving complex problems. Agile covers a larger arena with a well-defined set of values, concepts and principles. Scrum does fall under the expansive umbrella of Agile, but there are many other concepts like it. In addition, implementing Scrum doesn't mean you are Agile. To become agile, developing an agile mindset is extremely important. Implementing Scrum doesn't guarantee that you would become Agile but certainly helps build habits that can enhance Agility. Myth 3 – Cross Functionality means each team member should perform every task A cross-functional team is an efficient group of people who have a clear goal, representing various disciplines under the concerned organisation. The team's combined efforts are meant to add value to the process. Scrum Teams are, by nature, cross-functional. This does not mean every team member would display every kind of skill. It means the cross-functional attribute of the Scrum Team would benefit the group and organisation from an overall perspective. Read More >> About Author Venkatesh Rajamani has more than 15 years of experience delivering working software in short, feedback-driven cycles. He has helped a wide variety of organizations adopt agile software delivery practices, including large banking, payments, telecom, and product organizations. He started his career as a Software Engineer and spent almost 8 years as a hard-core Programmer. He has worked for or with large software delivery organizations including HP, IBM, Logica, Paypal, Ericsson, RBS and HID. He founded tryScrum.com in 2018 in order to execute his mission of Humanizing Organizations. Venkatesh is fluent in 4 languages. He is based in Chennai, India and sets the overall direction for tryScrum. He is the world’s first person to hold PKT, CAL-Educator, PST, CEC & CTC together. He loves reading books, travelling and public speaking.

Even a well-set team with clear objectives may fail to finish each thing when the Sprint ends.