Developing new programs to support the strategic direction of the organization. Creating and managing long-term goals. Developing a budget and operating plan for the program. Developing an evaluation method to assess program strengths and identify areas for improvement.

DUTIES & RESPONSIBILITIES:

• planning and designing the program and proactively monitoring its progress, resolving issues and initiating appropriate corrective action.
• defining the program’s governance arrangements.
• ensuring effective quality assurance and the overall integrity of the program – focusing inwardly on the internal consistency of the program, and outwardly on its coherence with infrastructure planning, interfaces with other programs and corporate, technical and specialist standards.
• managing the program’s budget on behalf of the SRO, monitoring expenditure and costs against delivered and realized benefits as the program progresses.
• facilitating the appointment of individuals to project teams.
• ensuring the delivery of new products or services from projects is to the appropriate level of quality, on time and within budget, in accordance with the program plan and program governance arrangements.
• ensuring there is allocation of common resources and skills within the program’s individual projects.
• managing third party contributions to the program.
• managing communications with all stakeholders.
• managing both the dependencies and the interfaces between projects.
• managing risks to the program’s successful outcome.
• working with the business change manager or equivalent on the transition to the new business as usual position.
• initiating extra activities and other management interventions wherever gaps in the programme are identified or issues arise.
• reporting the progress of the program at regular intervals to the SRO or program director if this role is also defined.

SKILLS:

• Program Management

1. Creates new programs when required.
2. Understands the vision/objective and kicks off new programs.
3. Manages and tracks Programs through its various phases.
4. Communicates progress/blockers with all stakeholders clearly and on time.

• Technical Acumen

1. Understands the system’s functionality and architecture down to its core components.
2. Participates in the design review process and influences decisions to ensure quality.
3. Applies engineering standards to the program and its dependencies.
4. Documents technical details to help broader audiences understand the delivered solutions.

• Communication Skills

1. Conveys information clearly and precisely to a wide range of stakeholders (Product Managers, Leadership Team, External Vendors, Testers, and Engineers).
2. Articulates technical concepts clearly to non-technical business users.
3. Negotiates and facilitates priorities and timelines.

• Leadership

1. Epitomizes servant leadership.
2. Owns with authority when required.
3. Displays the quality of being genuine.
4. Demonstrates trustworthiness and vision.

• Stakeholder & Partner Management

1. Collaborates with business partners to understand problems and envision workable solutions.
2. Gathers together different stakeholder groups and coordinates consensus on goals and product vision.
3. Negotiates with both internal and external partners on the timing of dependencies to ensure successful delivery.

• Influence

1. Exercises influence without authority, leading teams by example and behavior rather than mandate.
2. Builds a network of peers with trust as currency and a shared goal as the motivator.
3. Creates win-win scenarios in each collaborative effort to allow all stakeholders to progress with their own goals.

• Prioritization

1. Reassess backlog ona regular basis by the Effort-Value matrix to decide which goal to pursue.
2. Knows when to terminate tasks that lose relevance and initiates items that provide the most value to the program goal.
3. Communicates reasons for prioritization with all stakeholders.

• Multitasking

1. Switches between the six levels of Agile planning (from goal setting to daily planning) with ease.
2. Handles multiple conversations with different stakeholders (such as product managers, architects, developers, etc.) without losing the thread of conversation.