Balasubramanian Swaminathan

  

Sr.Project Manager (Sr. Scrum Master: Scrum of Scrum) / Agile Management Coach, CPP Inc.

Location: Mountain View, CA


Certifications

Certified Scrum Professional
Certified ScrumMaster

Biography

Balasubramanian Swaminathan has an overall 17+ years of experience in the R&D Software and IT Industry. Bala have worked in global multinational organizations in US, Germany and India.
To highlight a few R&D Software Industries: Medical Devices (Radiation Oncology); Security Software Solutions; Automotive Sector software solutions; Networking solutions; Radar communication.

Overall 6+ years of Agile Management experience (Agile Software development in Scrum and XP; Agile Coach in Scrum, Senior Scrum Master (Scrum of Scrum), Product Owner in Scrum; Agile Management Adjunct Instructor in UC Berkeley Extension).

Objective:
Bala's objective is to contribute in a Senior Management role (Portfolio Management, Chief Technology Consultant role), which requires an excellent Leadership, Communication, Negotiation and Technical skills.

Bala is a PMP, PMI-ACP, CSM(Certified Scrum Master), UC Berkeley Certified: Agile Management,Project Management,Project Human Factors & Team Dynamics

Specialties (To highlight few):
• PMO Strategic Management, Project Portfolio Management / Program Management (Agile Management) – managing multiple projects of varying complexity addressing diverse business objectives and processes
• Program development / Project Scoping / Business development - R&D (Product Development) and IT Software solution management using Agile Methodologies (Scrum)
• Responsible for providing direct program management for assigned, including cross-functional projects originating in Research & Product development, International Sales, Domestic Sales, Operations, and others designed to meet top customer and or corporate needs
• Ensure coordinated project releases in accordance with corporate strategies, priorities and established schedules, budget and scope
• Stakeholder Communication Management
• Customer Relationship; Cross Functional Team Leadership
• Process Improvement Solutions; CMMI Software model
• R&D Software Product Development - Real Time Application and Embedded Software Architecture using Object Oriented Analysis and Design techniques (Java, C++), Embedded Control Systems (Java, C++, C and Micro-controller programming), Real Time OS (VxWorks, QNX), Unix OS, SharePoint, MS Project Server, Clearcase, Visual Studio, Java Embedded development tools.

Work experience

UC Berkeley Extension, Adjunct Instructor (Agile Management)
September 2013 - Present, Berkeley, California, United States

Teaching/Coaching Agile Management courses to IT, Software and other professionals interested in learning Agile Management and Leadership topics during weekday nights (3 hours) and/or weekends (8 hours) in UC Berkeley Extension campus.

CPP Inc., Agile Coach / Sr.Project Manager (Sr.Scrum Master: Scrum of Scrum)
January 2013 - Present, Mt View, California, United States

Specific areas of responsibilities: 

Agile Coach

 i)    Promote agile process thinking in all applicable projects (publishing; translation; product development; IT development);

identify gaps in agile methodology understanding and help team follow the agile principles and practices.

 ii)   Create KANBAN board for all translation related projects. Work with all stakeholders (involves localization manager; IT

manager; publishing; research group).

 iii) Assist IT team (as agile coach) to oversee the “Sprint Retrospective” and other agile process that would help IT team to fully

understand the agile process.

 

Translation Program Management (Scrum Master) –

Oversee all translation related projects; assist localization manager in process related tasks (stage/gate process); perform project

retrospectives – gather team learning and help the new learning’s to be part of the next stage in the project or to be included in the

next project; identify and assist in filling the project gaps (if any) and deliver to the senior management a complete summary of all

translation projects performing a portfolio management role.

 

New Report Project Management (Scrum Master) –

Involve as Agile Project Manager representing PMO process (stage/gate process; agile process in creating user-stories; facilitate

cross-functional team meetings identifying, resolving project constraints; conduct phase/stage retrospective and to capture

learning’s and apply them in the next stage of the project.

 

Product Owner’s Prioritization group (Product Owner of Product Owners) –

Assist all Product owners as Agile Coach to discuss their requirements (bugs, issues to be fixed) in SK1, CPP.com and Web

Services; promote agile estimation and planning; identify along with product owners the top 10-15 items in the POP list.

 

IT/Software Management (Agile Coach):

Help the Software/QA team to facilitate the Sprint Retrospective. Follow the five principles of "Sprint Retrospective": Set the

stage, Gather the required data, Interpret the data, Decide what to do, Close the Retrospective. In this process, generate

learnings from the sprint retrospective, and the team own the action items, reports the progress made to the team in the daily

stand-up.

Siemens Medical Solutions USA Inc., Sr. Project Manager (Agile - Product Owner)
January 2012 - January 2013, Concord, California, United States

Radiation Oncology: Device Control System Software Development (Product Owner)

Performed analysis of customer installed base sites that have older Hand Control, Motor Control, Treatment Table, Multi-Leaf Collimator hardware/firmware/software. Prepared the cost-benefit analysis of older and new Hand Control, Motor Control, Treatment Table, Multi-leaf Collimator device solution and submitted a report to the sponsor for project approval (agile project chartering activities; setting the vision, mission, mission steps, system interaction diagram, cost benefit analysis).

Based on the project approval/Project Charter, Agile team (Scrum Team) started the project related activities by performing Sprint analysis/planning of customer requirements. Prepared the iterative SW and firmware design concepts (software and firmware); initiated development, integration test, and system test and produced test report and tracing report. Scrum team demonstrated the initial product increment and got the sponsor/customer approval. Review/plan for new changes/features to be added in next sprint of the project along with the team. Features are maintained by the Product Owner in the Product backlog. All product backlog items are prioritized based on internal/external customer feedback. As an agile PM, supported the entire process of understanding customer/stakeholders need, prioritizing them based on internal/external stakeholder needs, product backlog prioritization, pre-grooming user-stories, grooming w/ sprint team, sprint planning activities, help the scrum team to understand the user-story acceptance criterias, negotiating the acceptance criteria w/ scrum team, collaborated with internal customers to provide clarity in user-stories to scrum team, interfacing with scrum master on burn down charts, sprint velocity, the sprint report; facilitated/coached the team to follow scrum principles (Agile Methodology) along with scrum master.

Scrum team repeated the above agile approach for the entire duration of this project. Duration of each sprint is 4 weeks.

Agile Process followed: Scrum Methodology, Sprint Planning Meeting, Release Planning meeting, Agile roadmap for the entire project, Status/Stand-up meeting, Agile Demo, and Sprint retrospective. Scrum team comprised of following members: Agile PM (Scrum Master), Agile Coach and Product Owner (representing internal/external stakeholders). As the team was spread over different continents, Product owner along w/ scrum master performed "Scrum of Scrum" to oversee any integration issues; "Retrospective of Retrospective" to share the learnings across the different teams.

 

 

Siemens Medical Solutions USA Inc., Sr. Project Manager (Agile Product Owner)
May 2010 - December 2011, Concord, California, United States

 

Radiation Oncology–Handling CAPA (Corrective and Prevention Action), Customer critical Software/Firmware Complaints and Software solutions (Product Owner):

Scrum team (Product owner) performed analysis of customer complaints that are part of few CAPA (Corrective and Preventive Action) initiatives. Agile team (scrum development team) identified the components involved and performed risk analysis and classified the risk category (safety, performance and refinement) of the complaints.

During the scrum review/planning process: Scrum team started iterative analysis/planning of components involved; performed code review of the affected components; performed impact analysis for changes that are required; performed code fix, integration test; system integration test (at customer sites) released the SW patch to the affected customer sites with updated user docs. As an agile PM, supported the entire process of understanding customer issues, prioritizing them based on internal/external stakeholder needs, product backlog prioritization, pre-grooming user-stories, grooming w/ sprint team, sprint planning activities, help the scrum team to understand the user-story acceptance criterias, collaborated with internal customers to provide clarity in user-stories to scrum team, interfacing with scrum master on burn down charts, sprint velocity, the sprint report; facilitated/coached the team to follow scrum principles (Agile Methodology) along with scrum master.

Scrum team repeated the above iterative approach to handle the entire set of CAPA. Duration of each sprint cycle is 4 weeks.

Agile Process followed: Scrum Methodology, Sprint Planning Meeting, Release Planning meeting, Agile roadmap for the entire project, Status/Stand-up meeting, Agile Demo, and Sprint retrospective. Scrum team comprised of 5 team members, Agile PM (Scrum Master), Agile Coach and Product Owner (representing internal/external stakeholders). As the team was spread over different continents the team performed "Scrum of Scrum" to oversee any integration issues; "Retrospective of Retrospective" to share the learnings across the different teams.