The RTE role in Agile involves a number of responsibilities, including managing ART events and processes, communicating with stakeholders, escalating and tracking impediments, managing dependencies and risk, and encouraging collaboration between teams. It is the job of the RTE to facilitate program increment (PI) planning, create calendars to schedule them, and communicate this information to the relevant stakeholders. Show The role of an RTE in Agile is also to share additional knowledge with Scrum masters and other teams, ensure the processes operate within lean budgets and make sure teams understand and adhere to outlined guardrails. Becoming a Super Scrum master requires RTE Agile training that is held across a three-day course, where someone with extensive Scrum master experience learns more about the RTE role in Agile, and how to plan and implement a PI. Because ARTs typically include over 100 people, the RTE role in Agile requires advanced facilitation skills, vast knowledge of the Agile mindset, and strong communication and negotiation skills. This chapter is from the book SAFe Lean-Agile Leaders are lifelong learners and teachers who help teams build better systems through understanding and exhibiting the Lean-Agile Mindset, SAFe Principles, and systems thinking. Such leaders exhibit the behaviors below. #1 – Lead the ChangeThe work of steering an organization toward Lean and Agile behaviors, habits, and results cannot be delegated. Rather, Lean-Agile Leaders exhibit urgency for change, communicate the need for the change, build a plan for successful change, understand and manage the change process, and address problems as they come up. They have knowledge of organizational change management and take a systems view with respect to implementing the transformation. #2 – Know the Way; Emphasize Lifelong LearningCreate an environment that promotes learning. Encourage team members to build relationships with Customers and Suppliers and expose them to other world views. Strive to learn and understand new developments in Lean, Agile, and contemporary management practices. Create and foster formal and informal groups for learning and improvement. Read voraciously from the recommended reading list and on other topics. Share selected readings with others and sponsor book club events for the most relevant texts. Allow people to solve their own problems. Help them identify a given problem, understand the root causes, and build solutions that will be embraced by the organization. Support individuals and teams when they make mistakes, otherwise learning is not possible. #3 – Develop PeopleEmploy a Lean leadership style, one that focuses on developing skills and career paths for team members rather than on being a technical expert or coordinator of tasks. Create a team jointly responsible for success. Learn how to solve problems together in a way that develops people’s capabilities and increases their engagement and commitment. Respect people and culture. #4 – Inspire and Align with Mission; Minimize ConstraintsProvide mission and vision, with minimum specific work requirements. Eliminate demotivating policies and procedures. Build Agile Teams and trains organized around value. Understand the power of self-organizing, self-managing teams. Create a safe environment for learning, growth, and mutual influence. Build an Economic Framework for each Value Stream and teach it to everyone. #5 – Decentralize Decision-Making(See “SAFe Principle #9” for further discussion.) Establish a decison-making framework. Empower others by setting the mission, developing people, and teaching them to problem-solve. Take responsibility for making and communicating strategic decisions—those that are infrequent, long lasting, and have significant economies of scale. Decentralize all other decisions. #6 – Unlock the Intrinsic Motivation of Knowledge Workers(See “SAFe Principle #8” for further discussion.) Understand the role that compensation plays in motivating knowledge workers. Create an environment of mutual influence. Eliminate any and all management by objectives (MBOs) that cause internal competition. Revamp personnel evaluations to support Lean-Agile principles and values. Provide purpose and autonomy; help workers achieve mastery of new and increasing skills. Role of the Development ManagerAs an instantiation of the principles of Lean and Agile development, SAFe emphasizes the values of nearly autonomous, self-organizing, cross-functional teams and Agile Release Trains. This supports a leaner management infrastructure, with more empowered individuals and teams and faster, local decision-making. Traditional, day-to-day employee instruction and activity direction is no longer required. However, all employees still need someone to assist them with career development; set and manage expectations and compensation; and provide the active coaching they need to advance their technical, functional, individual, and team skills and career goals. They also have a right to serve as an integral member of a high-performing team. In addition, self-organizing ARTs do not fund themselves or define their own mission. That remains a management responsibility, as it is an element of implementation of strategy. Much of this responsibility traditionally falls to the traditional role of the development manager, and the adoption of Lean-Agile development does not abrogate their responsibilities. However, in SAFe these responsibilities fall to those who can adapt, thrive, and grow in this new environment. ResponsibilitiesThe development manager (or engineering manager for system development) is a manager who exhibits the principles and practices of Lean-Agile leadership as described above. Further, the manager has personal responsibility for the coaching and career development of direct reports, takes responsibility for eliminating impediments, and actively evolves the systems in which all knowledge workers operate. They have final accountability for effective value delivery as well. A summary of responsibilities is highlighted below. Personnel and Team Development
Program Execution
Alignment
Transparency
Built-in Quality
LEARN MORE [1] Manifesto for Agile Software Development. http://agilemanifesto.org/. [2] Reinertsen, Donald. The Principles of Product Development Flow: Second Generation Lean Product Development. Celeritas Publishing, 2009. [3] Rother, Mike. Toyota Kata: Managing People for Improvement, Adaptiveness, and Superior Results. McGraw-Hill, 2009. [4] Liker, Jeffrey and Gary L. Convis. The Toyota Way to Lean Leadership: Achieving and Sustaining Excellence Through Leadership Development. McGraw-Hill, 2011. |