[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Satyaprakash Joshii wrote:What can be an example situation where a non technical scrum master or a non technical project manager can do better than the technical ones?
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Jeanne Boyarsky wrote:
Satyaprakash Joshii wrote:What can be an example situation where a non technical scrum master or a non technical project manager can do better than the technical ones?
When the non-technical person has better PM or communication or facilitation skills. Remember that being technical is just one skill.
Satyaprakash Joshii wrote:
Jeanne Boyarsky wrote:
Satyaprakash Joshii wrote:What can be an example situation where a non technical scrum master or a non technical project manager can do better than the technical ones?
When the non-technical person has better PM or communication or facilitation skills. Remember that being technical is just one skill.
If someone is taken as non technical manager because he has better PM or communication or facilitation skills, still it would be always possible to have a person who has these PM or communication skills and facilitation skills as well as he is technical then why choose a non technical person .
A has good PM, communication, facilitation skills.
B has good PM, communicating, facilitation skills plus technical skills.
Then would one not choose B?
I worked in Israel's...I mean I did NOT work for the Mossad for 10 years. See my show - Who is America on youtube.
Satyaprakash Joshii wrote:
A has good PM, communication, facilitation skills.
B has good PM, communicating, facilitation skills plus technical skills.
Then would one not choose B?
Satyaprakash Joshii wrote:A has good PM, communication, facilitation skills.
B has good PM, communicating, facilitation skills plus technical skills.
Then would one not choose B?
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
As Jeanne said, such people probably prefer to use their technical skills.Satyaprakash Joshii wrote:. . . good PM, communicating, facilitation skills plus technical skills.
Then would one not choose B?
Jeanne Boyarsky wrote:
There are less B's in the world.
That isn't what Jeanne said.Satyaprakash Joshii wrote:. . . Is having good communication, facilitation and management skills so difficult for a technical person to have? . . .
Satyaprakash Joshii wrote:Is having good communication, facilitation and management skills so difficult for a technical person to have? I used to think developing skills to manage developers who have lesser experienced than one is a natural skills for a more experienced member of development team (technical person).
Satyaprakash Joshii wrote:Is having good communication, facilitation and management skills so difficult for a technical person to have? I used to think developing skills to manage developers who have lesser experienced than one is a natural skills for a more experienced member of development team (technical person).
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Jeanne Boyarsky wrote:
In any case, I wasn't talking about skills. I was talking about interests. .
Junilu Lacar wrote:
Leading is different from managing. Coaching and mentoring is different from managing. A senior technical person on a good agile team is a leader/coach/mentor, not a manager.
Junilu Lacar wrote:A good manager of an agile team spends most of their time looking outside of the team, finding opportunities and work for the team
Junilu Lacar wrote:A good manager of an agile team spends most of their time looking outside of the team, finding opportunities and work for the team
Junilu Lacar wrote: I'd encourage you to understand the difference between a Project Manager and a Scrum Master
Junilu Lacar wrote:
Leading is different from managing. Coaching and mentoring is different from managing. A senior technical person on a good agile team is a leader/coach/mentor, not a manager.
Satyaprakash Joshii wrote: i understand that he would be spending time outside team interacting lot with the customer and also with higher management. For 'finding opportunities and work for the team' , is it not the work of sales team rather than manager?
Satyaprakash Joshii wrote:Found the below link useful for understanding the differences between the roles of manager,scrum master ,leader.
https://aimconsulting.com/wp-content/uploads/2015/10/infographic_team-work_design_8.pdf
The product owner protects the project team from external stakeholders that want their requirements implemented.
The Scrum Guide wrote:The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.
The product owner is responsible for documenting requirements and their priority.
The Scrum Guide wrote:The Product Owner is ... responsible for ...:
* Clearly expressing Product Backlog items;
Satyaprakash Joshii wrote:Found the below link useful for understanding the differences between the roles of manager,scrum master ,leader.
https://aimconsulting.com/wp-content/uploads/2015/10/infographic_team-work_design_8.pdf
Satyaprakash Joshii wrote:Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person;
What does this mean ?
Junilu Lacar wrote:
Satyaprakash Joshii wrote:Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person;
What does this mean ?
other places, they refer to this as being "Full Stack".Essentially, the framers of Scrum don't care about the distinctions between DBA, Developer, Front-End guy, Back-End guy, etc. The team is expected to collaborate on the work and each member brings his or her own set of skills to bear on the problem.
Satyaprakash Joshii wrote:For instance if it is known that someone's title is DBA, then he would not be given say front end coding work and DBA work. If title is not looked into he may be given say front end coding work and he may waste time during the sprint as he may not have that skill .
Satyaprakash Joshii wrote:While the work will be assigned by development team itself, but within development team a front end coding work cannot be given to a DBA.For this would the dev team not require to know that one of their team member's title is DBA.?
Consider Paul's rocket mass heater. |