Please reply to talk about your experience working/starting in Agile Teams.I'll share some of my experiences about working in Scrum/Agile Teams below to kick it off.
My viewpoint is as the Scrum Master (SM), servant leader to the Team, and my key responsibilities are to facilitate agile practice within the Team and to help the Team collaborate with other teams externally. I'll break this down into a short series and the focus on those who begin on their Agile Teams
Where do we begin our Agile journey?
For me it was coming from a Project Management (PM) background, I was always interested in programming which I did at Uni. As a SM, different to a PM, we focus on the Team. First assess the Team's knowledge and experience with Agile, then work with the Team to set the field for work to begin. Each member of the Team works with their peers to get through the Backlog of tasks and Stories (User Stories). Getting up to speed with the terms and facets of Agile are where it all begins for each Team member. Agile is a mindset, it's not a step by step guide or a set of rules to follow, its about collaboration, getting work done together faster and how the Team works together to achieve this. A cohesive Team is where it all begins.
What do I bring to the Team?
This is a question for all of us when joining an Agile Team. Ask yourself, given the type of work to be completed and what roles are required to fulfill. You don't need to know specifics, just general areas like what language will be used (technical role), or what technology/platform is to be used or how do we get information for the work we will perform (Analysis role). This can inform you where you can contribute immediately or in the future (through learning). Those in Dev/technical roles will look at the tech and design specs, where as Analytical roles (BAs, Architects, Designers) will focus on other aspects like UX, CX and Business requirements. Each person contributes by calling on their experience and sharing knowledge with the Team. A key concept here is Value. We each want to be valuable to the Team which can be done in many different ways, perhaps to contribute in preparing requirements, or to create solutions to problems, write code or create assets for the solution, in engineering the platforms/systems that will host/facilitate the solution or to be that trusted person in front of the customer/user to gather/communicate information... the list goes on. The Team will talk through what is required to get work completed and they will also talk through what aspects bring Value to the Team. We focus on Being Agile.Who is the Team?
Some basics of Agile and Scrum: The Team is made up of 3 main Roles (Scrum):
i. Developers (Programmers, Designers/Architects, Engineers etc)
ii. Product Owner (can include BAs as well)
iii. Scrum Master
Remember these terms are just an easy to remember name for each Team member type to assist with entry into Agile and Scrum. The Team members in each Role often do more than the name might suggest, especially as Agile becomes more widespread, we find that organisations are asking more from each role especially in longer term/mature Agile Teams. For example, a Developer is not just a Programmer, the Developer role is the most generic and many individual role titles fit within it.
To illustrate this, I'll expand further in another post on the Roles by focusing on the flow of Development for typical Agile Teams.
To gauge the audience here and how to adapt my next post, please select the option that represents you in the poll.
My viewpoint is as the Scrum Master (SM), servant leader to the Team, and my key responsibilities are to facilitate agile practice within the Team and to help the Team collaborate with other teams externally. I'll break this down into a short series and the focus on those who begin on their Agile Teams
Where do we begin our Agile journey?
For me it was coming from a Project Management (PM) background, I was always interested in programming which I did at Uni. As a SM, different to a PM, we focus on the Team. First assess the Team's knowledge and experience with Agile, then work with the Team to set the field for work to begin. Each member of the Team works with their peers to get through the Backlog of tasks and Stories (User Stories). Getting up to speed with the terms and facets of Agile are where it all begins for each Team member. Agile is a mindset, it's not a step by step guide or a set of rules to follow, its about collaboration, getting work done together faster and how the Team works together to achieve this. A cohesive Team is where it all begins.
What do I bring to the Team?
This is a question for all of us when joining an Agile Team. Ask yourself, given the type of work to be completed and what roles are required to fulfill. You don't need to know specifics, just general areas like what language will be used (technical role), or what technology/platform is to be used or how do we get information for the work we will perform (Analysis role). This can inform you where you can contribute immediately or in the future (through learning). Those in Dev/technical roles will look at the tech and design specs, where as Analytical roles (BAs, Architects, Designers) will focus on other aspects like UX, CX and Business requirements. Each person contributes by calling on their experience and sharing knowledge with the Team. A key concept here is Value. We each want to be valuable to the Team which can be done in many different ways, perhaps to contribute in preparing requirements, or to create solutions to problems, write code or create assets for the solution, in engineering the platforms/systems that will host/facilitate the solution or to be that trusted person in front of the customer/user to gather/communicate information... the list goes on. The Team will talk through what is required to get work completed and they will also talk through what aspects bring Value to the Team. We focus on Being Agile.Who is the Team?
Some basics of Agile and Scrum: The Team is made up of 3 main Roles (Scrum):
i. Developers (Programmers, Designers/Architects, Engineers etc)
ii. Product Owner (can include BAs as well)
iii. Scrum Master
Remember these terms are just an easy to remember name for each Team member type to assist with entry into Agile and Scrum. The Team members in each Role often do more than the name might suggest, especially as Agile becomes more widespread, we find that organisations are asking more from each role especially in longer term/mature Agile Teams. For example, a Developer is not just a Programmer, the Developer role is the most generic and many individual role titles fit within it.
To illustrate this, I'll expand further in another post on the Roles by focusing on the flow of Development for typical Agile Teams.
To gauge the audience here and how to adapt my next post, please select the option that represents you in the poll.
