Is it Servant Leader or a True Leader?

Agile Leadership Scrum

Ashutosh Bhatawadekar Agile Consultant, Coach, Design Thinker & Transformation Lead| Consultant Pune, Maharashtra, India

What's the Good Word?
Remember the English Word Power game which used to come on Television in the Good Old Days of Indian Television??

Wondering based on the latest #Scrum Guide where they have replaced the word #servantleader with a #TrueLeader?
What's The the Good Word ?

Looking for Views, Thoughts and Perspectives here

Posted: Jan 22, 2021 4:04 AM (Updated by author: Jan 22, 2021 4:04 AM)

Sort By:

< 1 2 >

Paphatpisit Klinklan Regional Sourcing and Operation Manager| Krones (Thailand) Co., Ltd Samutprakan, Thailand

Feb 22, 2021 10:51 AM

Replying to Oliver Schneidemann

...

I seem to think that terminology is perhaps not what we need to focus on to practice better or understand our practice. Should discussions about leadership perhaps focus more on outcomes, instead of labels?

I'm totally agree with Oliver Schneidemann comment.

Posted: Mar 5, 2021 3:28 AM

Terrence Suttle Strategic IT Leader, Agile Advocate and complex project manager.| Fuzion I.T. Solutions Il, United States

A leader by any other name is just that... a leader. Do not get caught up on the change in Scrum, business and industries. Everyone needs someone to lead, follow and get out of the way. You do not have to bring war to lead. You have to be honest, direct, set real expectations and live where you are. Living where you are means do not fantasize about the end of the project, stay focused on the needs at this moment to get your team to their next phase. So if they decide to change the adjective, it still does not remove the fact that leaders are needed.

Posted: Sep 27, 2021 6:48 PM

Nway Nway Yangon, 06, Myanmar

As per my understanding, its depend on case by case and should use right leadership style for better outcome. sometime it could be used mix between two leadership styles

Posted: Sep 29, 2021 1:10 AM

Peter Morris PM Consultant, Author| INDUS Technology San Antonio Texas, United States

Develop the trick of thinking backwards. Thinking backwards means we visualize the end goal and then work backwards to determine what needed to happen to get there and what problems and risks may have occurred. It may seem strange to limit a discussion of requirements development and management to decomposition, prioritization and servant leadership. Remember, however, that most development problems begin with requirements, and how they are broken down into their component parts, prioritized for value and managed appropriately can spell the difference between high quality, increased velocity and stakeholder dissatisfaction.

Posted: Nov 12, 2021 5:29 PM

< 1 2 >

Please login or join to reply

Is it Servant Leader or a True Leader?

Sponsors

Vendor Events

Guessing is not a strategy: How to build decision velocity with AI and real-time data

Newsletters