This document discusses managing multiple simultaneous projects during an E-Business Suite upgrade. It describes a client that was upgrading EBS while also upgrading their database, payroll/sales tax software, changing hardware, reimplementing receivables, restructuring accounts, and launching new modules. The presentation covers assembling a project team, defining roles, developing an approach, prioritizing work, adapting to changes, ensuring quality, and preparing for go-live. It emphasizes testing, communication, and flexibility to manage complex, interdependent projects on time and on budget.
Phillip Hughey is an experienced technical project manager, Scrum Master, and Product Owner based in Chattanooga, TN. He has over 15 years of experience managing complex software projects using agile methodologies like Scrum and Kanban. Currently he is a project manager at Blue Cross Blue Shield of TN where he leads their Solution Lifecycle Management and Source Code Migration projects. He has professional certifications in Scrum and ITIL and has managed projects ranging from $1M to $1.2M.
Presentation how a traditional project manager transforms to scrum - finalSadaf Saad
This document provides a mapping between traditional project management practices from PMBOK and agile/Scrum practices. It summarizes the key aspects of traditional project management and PMBOK, and then shows how each of the PMBOK knowledge areas (integration management, scope management, time management, etc.) align with similar processes in Scrum. The mapping demonstrates that while the approaches are different, the essential functions of project management can still be fulfilled within an agile framework like Scrum.
The core concepts of a Release Based development lifecycle for NES projects.
The lifecycle starts with the Product Roadmap, showing what Capabilities are provided in what order, in what Epic, to deliver the needed business value, on the needed dates, for the needed cost, with the needed Features.
The Features and Stories that implement these Capabilities are traceable to the Product Roadmap to show Physical Percent Complete from starting at the Story flowing to a Capability to deliver a needed Capability.
WBS Compliance Challenges for Agile ERP ProjectsGlen Alleman
Agility implies a systematic vision of the outcome - an intelligent or ingenium that makes it possible to connect seperate entities and their outcomes in a rapid and suitable manner
This document provides an overview of risk management for project sponsors. It discusses key project management concepts like the project management process, roles and responsibilities of sponsors and managers, and the importance of managing scope, schedule and budget. It then covers the risk management process, including identifying common risks like schedule and budget slippage, lack of clear requirements, and ineffective sponsorship. It provides symptoms, consequences and mitigating actions for addressing each risk.
This document provides an overview of basic software engineering concepts across 20 pages. It covers topics such as software engineering, the software development life cycle, software project management, software requirements, software design, user interface design, and software complexity. For each topic, it provides definitions and descriptions of key terms, processes, methodologies, techniques, and tools. The document is intended as an introductory guide to software engineering fundamentals.
The core concepts of a Release Based development lifecycle for agile enterprise projects.
The lifecycle starts with the Product Roadmap, showing what Capabilities are provided in what order, in what Capability, to deliver the needed business value, on the needed dates, for the needed cost, with the needed Features.
The Features and Stories that implement these Capabilities are traceable to the Product Roadmap to show Physical Percent Complete from starting at the Story flowing to a Capability to deliver a needed Capability.
Phillip Hughey is an experienced technical project manager, Scrum Master, and Product Owner based in Chattanooga, TN. He has over 15 years of experience managing complex software projects using agile methodologies like Scrum and Kanban. Currently he is a project manager at Blue Cross Blue Shield of TN where he leads their Solution Lifecycle Management and Source Code Migration projects. He has professional certifications in Scrum and ITIL and has managed projects ranging from $1M to $1.2M.
Presentation how a traditional project manager transforms to scrum - finalSadaf Saad
This document provides a mapping between traditional project management practices from PMBOK and agile/Scrum practices. It summarizes the key aspects of traditional project management and PMBOK, and then shows how each of the PMBOK knowledge areas (integration management, scope management, time management, etc.) align with similar processes in Scrum. The mapping demonstrates that while the approaches are different, the essential functions of project management can still be fulfilled within an agile framework like Scrum.
The core concepts of a Release Based development lifecycle for NES projects.
The lifecycle starts with the Product Roadmap, showing what Capabilities are provided in what order, in what Epic, to deliver the needed business value, on the needed dates, for the needed cost, with the needed Features.
The Features and Stories that implement these Capabilities are traceable to the Product Roadmap to show Physical Percent Complete from starting at the Story flowing to a Capability to deliver a needed Capability.
WBS Compliance Challenges for Agile ERP ProjectsGlen Alleman
Agility implies a systematic vision of the outcome - an intelligent or ingenium that makes it possible to connect seperate entities and their outcomes in a rapid and suitable manner
This document provides an overview of risk management for project sponsors. It discusses key project management concepts like the project management process, roles and responsibilities of sponsors and managers, and the importance of managing scope, schedule and budget. It then covers the risk management process, including identifying common risks like schedule and budget slippage, lack of clear requirements, and ineffective sponsorship. It provides symptoms, consequences and mitigating actions for addressing each risk.
This document provides an overview of basic software engineering concepts across 20 pages. It covers topics such as software engineering, the software development life cycle, software project management, software requirements, software design, user interface design, and software complexity. For each topic, it provides definitions and descriptions of key terms, processes, methodologies, techniques, and tools. The document is intended as an introductory guide to software engineering fundamentals.
The core concepts of a Release Based development lifecycle for agile enterprise projects.
The lifecycle starts with the Product Roadmap, showing what Capabilities are provided in what order, in what Capability, to deliver the needed business value, on the needed dates, for the needed cost, with the needed Features.
The Features and Stories that implement these Capabilities are traceable to the Product Roadmap to show Physical Percent Complete from starting at the Story flowing to a Capability to deliver a needed Capability.
The document discusses various techniques for continuous improvement in agile projects, including:
1. Agile projects schedule continuous improvement activities like retrospectives into each iteration to regularly adapt processes. This helps make continuous learning habitual.
2. Techniques for process improvement include kaizen for small incremental changes, process tailoring to fit each project, and systems thinking to understand a project's complexity.
3. Techniques for product improvement include value stream mapping, project post-mortems, and seeking frequent customer feedback through demonstrations. Continuous improvement is never finished and aims to benefit both the current and future projects.
Calculating Physical Percent Complete on Agile ProjectsGlen Alleman
Developing software using Scrum still needs the ability to determine the Estimate to Complete (ETC), the Estimate at Completion (EAC), and the Estimated Completion Data (ECD) when there is a fixed deliverable date, a fixed budget for that software, and a minimal set of Features and Capabilities on that date for that budget
The document outlines Radix Development Methodology which includes a project initiation process involving internal kick-off meetings, project registration, and formal introductions. It also describes communication through a project email group, monitoring progress using Redmine and Resource Scheduling System, conducting project closure activities like collecting feedback and documenting lessons learned. Contact details are provided at the end.
The document outlines an upcoming Agile and Scrum workshop. It provides biographical information about the trainer, Nguyen Thanh Phuoc, and an overview of the workshop agenda, which includes lectures, exercises, questions and answers, and discussions. The document also lists some reference materials that will be used and criteria for successful completion of the workshop, which requires active participation in all classroom activities.
TotalSoft introduced in Romania the project management concept through Oracle Primavera, the project management application mostly used by the local market.
Currently, TotalSoft has a portfolio of over 650 Primavera customers in areas such as public administration, construction, engineering, shipbuilding, defense, energy and oil, accounting for 90% of the project management solutions market in Romania. These results, along with the technical skills held, allowed obtaining the Oracle Platinum Partner status, TotalSoft being the only company in Romania to hold this title for the Oracle Primavera specialization.
In fact, TotalSoft managed to be elected for 11 consecutive years in the Primavera Club President, where are recruited only partners with outstanding results. Moreover, only 7 companies in the world have managed to enter this exclusive circle. In over 17 years of experience in this field, TotalSoft completed the Oracle Primavera suite with a series of applications tailored to the local specificity, but also with consulting services, maintenance, technical support and training in project management.
This document discusses software project management concepts and processes used at Infosys, a large software company. It covers several key topics:
- The importance of project management and following defined processes. Infosys uses the CMM framework and aims for high maturity.
- How Infosys manages projects, including training for project managers, defining project plans and tracking status during execution.
- The infrastructure used for planning, including a process database of past projects, process capability baselines, and process assets like templates.
- How Infosys tailors its standard development process based on project characteristics. It also describes the change management process.
- The document concludes by covering effort estimation and scheduling concepts used
The document provides a summary of Kevin J. Fox's experience as a Program Manager, Project Manager, and Engagement Manager. He has over 12 years of experience successfully managing projects over $10 million budgets and teams of up to 50 members. He is experienced in Agile project management methodology and global organizations. His background includes software development, program management, project management, engagement management, and experience in various industries.
Credible Plans, Integrated Reporting, and Control SystemsGlen Alleman
Project success starts with a credible plan for delivering the needed capabilities as planned. This starts with knowing what Done looks like in units of measure meaningful to the decision makers.
Now, it is final! PMI- Project Management Institute to publish PMBOK 6th edition officially . But what is changing from the PMBOK 5th edition to PMBOK 6th edition? How will the PMBOK 6th edition change impact us? Let us dig deeper to understand what changes in PMBOK 6th edition and what does not and how and whom it will impact. We will summarize the changes in PMBOK 6th edition in this Presentation.
Performance-Based Management
integrates Principles, Practices, and Processes
– to assure actionable information is provided to the decision makers that can increase the Probability Of Program Success.
Successful projects deliver capabilities:
§ Not work efforts,
§ Not cost expenditures,
§ Not documentation, test results, or the processes.
§ These all needed, but they’re not the deliverables.
§ For success projects must deliver tangible beneficial outcomes, assessed in units of measure meaningful to the decision makers.
This slide deck is an extract from the Book of the same name https://www.amazon.com/Performance-Based-Project-Management-Increasing-Probability/dp/0814433308
The document discusses some key issues with conventional software management approaches like the waterfall model. It notes that software development is unpredictable and that management discipline is more important for success than technology. Some problems with the waterfall model are late risk resolution, adversarial stakeholder relationships due to rigid documentation requirements, and a focus on documents over engineering work. The document also provides metrics on the relative costs of development versus maintenance and how people are a major factor in productivity.
Applying Agile principles, principles, and processes to the CODE
program. Building the Release Plan for each program event and the deliverables for that review.
Physical Percent Complete is a primary measure of progress to plan for all project work. For Agile projects, this is a critical success factor. Here's how
Lean planning with Oracle Primavera CloudPRMYAZILIM
For decades now, two project-management and scheduling methodologies have dominated the world of engineering and construction: lean and critical path method (CPM).
Lean looks at tasks in granular detail, identifying the most efficient and collaborative way to complete each of them—making it extremely popular with field coordinators and teams. It can add a huge amount of value to any construction project. In fact, a recent Dodge Data and Analytics study found that projects that heavily relied on lean were three times more likely to complete ahead of schedule and two times more likely to complete under budget.
Integrated Program Performance ManagementGlen Alleman
Integrated Program Performance Management elements are organization planning schedule applied to increase the probability of program success on traditional and agile programs.
The document provides an overview of software project management. It defines what a project and software project are, discusses key characteristics of projects, and compares projects to operations. It also outlines important aspects of project management including the project management process groups, knowledge areas, factors that influence projects, and the roles of the project manager, project management office, and how organizational structure can affect a project.
Building a Credible Performance Measurement Baseline (PM Journal)Glen Alleman
Establishing a credible Performance Measurement Baseline, with a risk adjusted Integrated Master Plan and Integrated Master Schedule, starts with the WBS and connects Technical Measures of progress to Earned Value
eCIO PPT Roles for a SAP and Systems Integration ProjectDavid Niles
The document outlines the roles and responsibilities of an IT Project Management Office (PMO) for a large Systems Integration project using the ASAP (Accelerated SAP) methodology. It describes the six phases of the ASAP methodology and provides details on deliverables, milestones, and objectives for each phase. It also defines the roles of various project managers, administrators, and SAP specialists involved in the project and how they would be organized and report within the proposed PMO structure.
Meyyappan Sundrarajulu has over 22 years of experience as an IT Program Manager leading large, complex software projects across multiple industries. He has a track record of successfully delivering projects on time and within budget by planning, scheduling, and overseeing all aspects of the project lifecycle. Currently he is the Program Manager at Snapbizz Cloudtech Pvt Ltd where he has helped scale their POS and billing systems and develop new hardware and software releases.
Project Management: Choosing the Right Tools and ApproachPeter Campbell
Different projects require difgferent approaches. It's not a matter of which is better - traditional Waterfall or the newer agile approach -- it's a matter of what type of project your doing,. This NTEN presentation discusses both approaches and advises on when each one might work, as well as discussing what software will help.
The document discusses various techniques for continuous improvement in agile projects, including:
1. Agile projects schedule continuous improvement activities like retrospectives into each iteration to regularly adapt processes. This helps make continuous learning habitual.
2. Techniques for process improvement include kaizen for small incremental changes, process tailoring to fit each project, and systems thinking to understand a project's complexity.
3. Techniques for product improvement include value stream mapping, project post-mortems, and seeking frequent customer feedback through demonstrations. Continuous improvement is never finished and aims to benefit both the current and future projects.
Calculating Physical Percent Complete on Agile ProjectsGlen Alleman
Developing software using Scrum still needs the ability to determine the Estimate to Complete (ETC), the Estimate at Completion (EAC), and the Estimated Completion Data (ECD) when there is a fixed deliverable date, a fixed budget for that software, and a minimal set of Features and Capabilities on that date for that budget
The document outlines Radix Development Methodology which includes a project initiation process involving internal kick-off meetings, project registration, and formal introductions. It also describes communication through a project email group, monitoring progress using Redmine and Resource Scheduling System, conducting project closure activities like collecting feedback and documenting lessons learned. Contact details are provided at the end.
The document outlines an upcoming Agile and Scrum workshop. It provides biographical information about the trainer, Nguyen Thanh Phuoc, and an overview of the workshop agenda, which includes lectures, exercises, questions and answers, and discussions. The document also lists some reference materials that will be used and criteria for successful completion of the workshop, which requires active participation in all classroom activities.
TotalSoft introduced in Romania the project management concept through Oracle Primavera, the project management application mostly used by the local market.
Currently, TotalSoft has a portfolio of over 650 Primavera customers in areas such as public administration, construction, engineering, shipbuilding, defense, energy and oil, accounting for 90% of the project management solutions market in Romania. These results, along with the technical skills held, allowed obtaining the Oracle Platinum Partner status, TotalSoft being the only company in Romania to hold this title for the Oracle Primavera specialization.
In fact, TotalSoft managed to be elected for 11 consecutive years in the Primavera Club President, where are recruited only partners with outstanding results. Moreover, only 7 companies in the world have managed to enter this exclusive circle. In over 17 years of experience in this field, TotalSoft completed the Oracle Primavera suite with a series of applications tailored to the local specificity, but also with consulting services, maintenance, technical support and training in project management.
This document discusses software project management concepts and processes used at Infosys, a large software company. It covers several key topics:
- The importance of project management and following defined processes. Infosys uses the CMM framework and aims for high maturity.
- How Infosys manages projects, including training for project managers, defining project plans and tracking status during execution.
- The infrastructure used for planning, including a process database of past projects, process capability baselines, and process assets like templates.
- How Infosys tailors its standard development process based on project characteristics. It also describes the change management process.
- The document concludes by covering effort estimation and scheduling concepts used
The document provides a summary of Kevin J. Fox's experience as a Program Manager, Project Manager, and Engagement Manager. He has over 12 years of experience successfully managing projects over $10 million budgets and teams of up to 50 members. He is experienced in Agile project management methodology and global organizations. His background includes software development, program management, project management, engagement management, and experience in various industries.
Credible Plans, Integrated Reporting, and Control SystemsGlen Alleman
Project success starts with a credible plan for delivering the needed capabilities as planned. This starts with knowing what Done looks like in units of measure meaningful to the decision makers.
Now, it is final! PMI- Project Management Institute to publish PMBOK 6th edition officially . But what is changing from the PMBOK 5th edition to PMBOK 6th edition? How will the PMBOK 6th edition change impact us? Let us dig deeper to understand what changes in PMBOK 6th edition and what does not and how and whom it will impact. We will summarize the changes in PMBOK 6th edition in this Presentation.
Performance-Based Management
integrates Principles, Practices, and Processes
– to assure actionable information is provided to the decision makers that can increase the Probability Of Program Success.
Successful projects deliver capabilities:
§ Not work efforts,
§ Not cost expenditures,
§ Not documentation, test results, or the processes.
§ These all needed, but they’re not the deliverables.
§ For success projects must deliver tangible beneficial outcomes, assessed in units of measure meaningful to the decision makers.
This slide deck is an extract from the Book of the same name https://www.amazon.com/Performance-Based-Project-Management-Increasing-Probability/dp/0814433308
The document discusses some key issues with conventional software management approaches like the waterfall model. It notes that software development is unpredictable and that management discipline is more important for success than technology. Some problems with the waterfall model are late risk resolution, adversarial stakeholder relationships due to rigid documentation requirements, and a focus on documents over engineering work. The document also provides metrics on the relative costs of development versus maintenance and how people are a major factor in productivity.
Applying Agile principles, principles, and processes to the CODE
program. Building the Release Plan for each program event and the deliverables for that review.
Physical Percent Complete is a primary measure of progress to plan for all project work. For Agile projects, this is a critical success factor. Here's how
Lean planning with Oracle Primavera CloudPRMYAZILIM
For decades now, two project-management and scheduling methodologies have dominated the world of engineering and construction: lean and critical path method (CPM).
Lean looks at tasks in granular detail, identifying the most efficient and collaborative way to complete each of them—making it extremely popular with field coordinators and teams. It can add a huge amount of value to any construction project. In fact, a recent Dodge Data and Analytics study found that projects that heavily relied on lean were three times more likely to complete ahead of schedule and two times more likely to complete under budget.
Integrated Program Performance ManagementGlen Alleman
Integrated Program Performance Management elements are organization planning schedule applied to increase the probability of program success on traditional and agile programs.
The document provides an overview of software project management. It defines what a project and software project are, discusses key characteristics of projects, and compares projects to operations. It also outlines important aspects of project management including the project management process groups, knowledge areas, factors that influence projects, and the roles of the project manager, project management office, and how organizational structure can affect a project.
Building a Credible Performance Measurement Baseline (PM Journal)Glen Alleman
Establishing a credible Performance Measurement Baseline, with a risk adjusted Integrated Master Plan and Integrated Master Schedule, starts with the WBS and connects Technical Measures of progress to Earned Value
eCIO PPT Roles for a SAP and Systems Integration ProjectDavid Niles
The document outlines the roles and responsibilities of an IT Project Management Office (PMO) for a large Systems Integration project using the ASAP (Accelerated SAP) methodology. It describes the six phases of the ASAP methodology and provides details on deliverables, milestones, and objectives for each phase. It also defines the roles of various project managers, administrators, and SAP specialists involved in the project and how they would be organized and report within the proposed PMO structure.
Meyyappan Sundrarajulu has over 22 years of experience as an IT Program Manager leading large, complex software projects across multiple industries. He has a track record of successfully delivering projects on time and within budget by planning, scheduling, and overseeing all aspects of the project lifecycle. Currently he is the Program Manager at Snapbizz Cloudtech Pvt Ltd where he has helped scale their POS and billing systems and develop new hardware and software releases.
Project Management: Choosing the Right Tools and ApproachPeter Campbell
Different projects require difgferent approaches. It's not a matter of which is better - traditional Waterfall or the newer agile approach -- it's a matter of what type of project your doing,. This NTEN presentation discusses both approaches and advises on when each one might work, as well as discussing what software will help.
Principal Financial Group: Stretching CRM Capabilities with Pivotal 6.0Aptean
The document discusses an upgrade of Principal Financial Group's Pivotal CRM system from version 5.9 to 6.0.8. It involved over 23,000 hours of work over 10 months and included challenges like maintaining functionality for ongoing business needs, tight timelines, and extensive customizations over 13+ years. Innovations that helped overcome risks included automating regression testing, operating a 24-hour project team with global resources, shifting schedules, and prioritizing testing based on business and technical risk. Third parties provided over 25% of the hours to help complete the complex upgrade successfully ahead of a key year-end deadline.
Robert J. Vandenberg has over 30 years of experience in project management, IT management, and leadership. He has managed projects with budgets up to $5.5 million. Currently, he works as a consultant providing Scrum coaching and assisting with transitions to Agile methodologies. Previously, he has held roles managing releases, implementations, and teams for companies including Intapp, West Marine, Plutora, Cisco, IBM, and Microsoft.
Mark Luongo is an experienced Project Management Professional with over 30 years of experience managing projects in various industries including IT, infrastructure, supply chain, and product development. He has extensive experience managing multi-million dollar projects on schedule and within budget at companies including ABB, IBM, Progress Energy, and as an independent contractor.
Modernizing the Back-office to improve the sporting fan's experience with IB...IBM
In this session learn how Maple Leaf Sports & Entertainment (MLSE) transformed its finance and procurement system to enable better decision-making processes for brand recognition, fan loyalty, and overall fan experience. MLSE is Canada’s leader in delivering top-quality sports and entertainment experiences. It owns several professional sports franchises and the venues its teams play and train in. It also provides fans with music and entertainment. Hear how IBM helped transition MLSE from manual processes and the Great Plains legacy system to best-in-class business processes in an on-time, on-budget implementation of Oracle ERP Cloud in seven months, to quickly lay down the financial backbone of its transformation journey.
The document discusses establishing a Project Control Office (PCO) to provide project management practices and oversight. It outlines the changing role of IT from support to strategic enabler of business transformation. A PCO's responsibilities include managing project plans, budgets, schedules and issues. Examples of tools include status reports, scorecards and a master project plan template. Establishing a PCO can help projects complete within 5% of budget and schedule compared to 10-50% over without one. The ROI comes from identifying issues earlier to minimize impacts. Next steps to create an effective PCO include buy-in, dedicated resources, and tools.
Benefits of implementing primavera p6 r8.1 and integration to oracle pptp6academy
The document discusses the benefits of upgrading Primavera P6 and integrating it with Oracle at DRS Defense Solutions. Key points include:
- DRS upgraded from Primavera P6 R7 to R8.1 and Oracle EBS 11.5.10 to R12 to establish a global program management framework.
- Challenges included the transition to a web platform in P6, complex data migration between the old and new systems, and coordination between implementation teams.
- Benefits of the new system include global resource planning, standard WBS/CBS templates, common project codes for reporting, and potential future links to risk management and operations data.
- Lessons learned
PROFESSIONAL SUMMARY
Program / Project Manager with a successful record of managing full project life-cycle initiatives. Expertise includes a combination of both Application Development and Infrastructure experience. I’ve acted as both developer and then App Dev PM while with the State of Missouri. I rate my SDLC experience as an 8/10 as I personally did VB development and acted as the PM for entire application delivery from development through SQL and into production. An exceptionally strong Program / Project Manager with the following qualifications:
• PM experience covers product planning, scheduling, testing, change management, implementations and ROI analysis
• Successfully managed projects for domestic and international corporations including BP, State of MO-DOR, Salton/Toastmaster
• Recognized for surpassing corporate and customer expectations for quality and focus by configuring, implementing, training, mergers and acquisitions
• Experienced in handling projects in rapidly changing functional, procedural and engineering environments including international offshore (Brazil, Columbia, UK, Trinidad, Argentina, Mexico) testing/development teams
• Provides disciplined, assertive, tactful leadership to resolve challenges in an efficient, cost-effective manner
• Skilled in developing and maintaining strong customer relations and fostering cohesive, consensus-building project team interactions
• Recognized for being a highly-motivated, self-directed, enthusiastic project manager with a positive, creative attitude for balancing schedules, costs and priorities
• Recognized as an “idea leader” with flexibility to handle assignments with analytical test equipment and to develop quality assurance best practices/processes
• Excels in developing and maintaining project plans without being dependent on technical resources for input.
• Successfully transitioned to a portfolio of 65 projects International with a blend of waterfall and agile teams with ~$75 million budget. Overseeing multiple vertical project managers, business analyst, functional analyst, and working with the communications team. All in a ~2 month onboarding to the account.
• Apply communication strategies to engage International-level stakeholders in order to understand product objectives, customer service processes, development teams, and define strategies for opposing developing techniques to timely and with budget constraints. Supports SAFe (Scaled Agile Framework) as the “Release Train Engineer.
• Manage the flow of value through the program and value stream Kanban’s to increase outlook into new work and into the work flow. Establishing connections among the Portfolio, Journey mapping, value stream, and programs levels.
Applying both of waterfall and iterative developmentDeny Prasetia
This document discusses applying both waterfall and iterative development models to a project to develop a tool with minimum functionality in a short time for an operating lease business. It identifies challenges of growing business needs, lack of standardized processes and manual data entry. An assessment is proposed to clarify requirements and scope. Both waterfall and iterative development models are described. The document recommends using iterative development within the waterfall model to allow for prototyping, user feedback and flexibility to changes. Key success factors include collaborative teams, monitoring progress daily, and continual improvement between iterations. Lessons focus on managing risks, quality processes and using story point estimation.
This resume is for Kevin J. Fox, an experienced Project Manager and IT professional with over 11 years of experience managing technical projects and teams. He has a proven track record of successfully delivering large, multi-million dollar projects on time and under budget across various industries. He possesses strong leadership, communication, budgeting, and project management skills.
The document provides an executive summary and resume for Kevin J. Fox, an experienced Program/Project Manager with over 20 years of experience successfully managing projects up to $10M budgets and 50-member teams across various industries. Fox has a strong background in Agile project management methodologies and experience delivering technical solutions on time and under budget. He provides expertise in strategic planning, project management, engagement management, software development, and leadership.
Kevin J. Fox is an experienced senior project/program manager with over 20 years of experience successfully managing projects up to $10M budgets and teams of 50 members. He has expertise in strategic planning, Agile/Scrum methodology, software development, and global project management. His background includes managing projects in industries such as healthcare, financial services, consumer goods, and government.
Converting from a three tier or monolithic application to microservices can be daunting, and often comes at a non-trivial cost or effort. So why are organizations doing it, and how do they justify the expense? We will discuss some of the practices and migration strategies used by organizations who undergo this sort of transformation, such as extracting functions through refactoring and converting them to microservices. As the journey progresses, we learn that there is no one-size-fits-all approach to making applications cloud-native… so the real question needs to be ‘how do I find the right approach for me?’ We can help you begin to answer that question for yourself, by discussing the facets of consideration such as technical, procedural, and risk tolerance to name a few.
Leveraging DevOps Principles for Release and DeploySerena Software
This document discusses leveraging DevOps principles for improving software release and deployment processes. It notes that while agile development has increased innovation speed, it has pushed bottlenecks to IT operations due to differing goals between development and operations teams. To address this, the document recommends applying DevOps principles such as automating processes, keeping all code and configurations in version control, integrating release and deployment tools, and establishing continuous delivery practices to create repeatable, reliable processes that improve responsiveness to business needs.
The document is a resume for Kevin J. Fox that summarizes his experience as a manager of IT services and project manager with over 10 years of experience. He has a track record of delivering technical solutions on time and under budget for large organizations. His skills include strategic planning, vendor management, project management, sales support, and leading teams. His most recent experience is as a senior project manager at MedAssets where he manages development teams and completes projects on time.
Kevin Fox is a manager with over 10 years of experience delivering technical solutions and improving processes. He has experience managing multi-million dollar budgets and projects. His background includes roles in project management, technical sales support management, and strategic planning. He provides an overview of his skills, experience managing teams, and history of successfully completing projects on time and under budget across various industries.
Patricia McGrady is an experienced IT project manager and solutions architect based in Florida who has successfully led teams and complex projects across various industries, delivering on time and on budget. She has over 20 years of experience managing projects of all sizes using different methodologies and has a proven track record of improving processes, increasing customer satisfaction and driving cost savings. Her background includes positions at IBM, Office Depot, and other companies where she specialized in project management, infrastructure solutions, and managing technical teams.
Ambrose Naveen Veigas is a project manager with over 12 years of experience in information technology infrastructure services, ITES technical support, and customer service. He has expertise in project management, program management, service management, desktop engineering, data center management, and service desk management. Currently working as part of the TCS PMCOE team, he is pursuing his PMP certification and has extensive experience managing projects for clients in various industries.
Similar to Managing Multiple Projects Within E-Business Suite Upgrade_PPT (20)
Managing Multiple Projects Within E-Business Suite Upgrade_PPT
1. Session ID:
Prepared by:
Managing Multiple Projects
Within E-Business Suite
Upgrade
10331
@KLambert61
Kyle Lambert
Senior Director, Solutions
EiS Technologies, Inc.
Kyle.Lambert@EiSTech.com
2. Abstract
How do you manage multiple simultaneous projects
without losing focus on the key objective or slipping
deadlines?
Upgrading E-Business Suite is challenging all by itself.
However, when you need to upgrade your database
version, payroll tax software and sales tax software,
while changing hardware architecture, re-implementing
your Receivables implementation and restructuring
your Chart Of Accounts, plus adding launching
Manager Self-Service and an externally accessible
employee portal.
2
5. Agenda
• About The Presenters/Audience
• About EiS Technologies, Inc.
• Who Was The Client?
• Client’s Timing and Motivation
• What Was The Client’s Challenge?
• Creating The Project Team
• Team Roles
• Developing Project Approach
• Putting First Things First
• Keeping Projects On Track
• Adapting To Changes
• Assuring Quality
• Preparing For Go Live
• Measuring Success
• Q&A
5
6. About The Presenters/Audience
• Presenter & Contributors:
– Kyle Lambert – Senior Director, Solutions
• Audience Profile:
– Running E-Business Suite R11? R12?
– Planning an upgrade?
– Project Managers? Project Leads?
– Use managed service?
– Hosted?
– Have a segment of your ecosystem in the cloud?
– Totally in the cloud?
6
7. About EiS Technologies, Inc.
7
At EiS Technologies, we create tangible value for our
clients by providing powerful and cost effective
solutions that enable efficiencies throughout the
organization.
From Reporting and BI, to integrations, implementations,
and upgrades, we stand by our clients, both as partners,
trusted advisors, and friends.
8. Who Was The Client?
• Leader in Quick Serve Restaurant (QSR) industry
• Hundreds of Franchisees & Corporate sites
• Rapidly growing through organic growth and
marketing magic
• Initiatives to drive operational efficiencies
• Privately owned
8
9. Client’s Timing and Motivation
• In late 2014, this QSR giant decided to upgrade EBS Applications from
R11i to R12.1.3
• After a project assessment in December of 2014, the project team was
assembled and a preliminary upgrade plan developed
• The upgrade started in January of 2015
• Challenged with a number of software de-support issues, the company
needed:
– To prepare for explosive corporate growth
– To gain better business efficiencies by implementing new EBS modules
– To move from software laggard to main stream adopter
– To create a foundation for adding new functionality and increased productivity
– To create a hub into which all business process could feed and integrate
• A few business optimization projects were also included in the upgrade
effort. These additional work streams were incredibly important to the
business users and management team.
• Although the additions added complexity to the upgrade, the tasks were
included in the plan and delivered as part of the on-time, on-budget project
9
10. What Was The Client’s Challenge?
• EBS upgrade from 11.5.10.2 to 12.1.3
• Database upgrade 10.2.0.4 to 11.2.04
• Migrate hardware architecture from 32- bit to 64-bit
• Re-Structure the General Ledger Chart Of Accounts
• Re-implement Receivables
• Develop a custom Receivables Portal
• Implement HR Manager Self-Service
• Decommission Discoverer
• Upgrade Vertex Payroll Tax to a supported version
• Upgrade Sabrix Sales Tax to a supported version
• Migrate from 3rd party check printing to in-house
• Fold in all R11 changes through the final CRP
• All in 9 months – The end date could not be missed
10
11. Creating The Project Team
Assemble Multi-Faceted Project Team
– Client Project Manager
– Implementer Project Manager
– Technical Liaison
– Operations Manager
– Communications Manager
11
12. Team Roles
Client Project Manager
– Managing the scope of the projects
– Reviewing & maintaining all budgets
– Assuring milestones & adjusted priorities are
known to project team
– Identifying resources for each sub-project
– Identifying all client efforts
– Supervising project teams
– Being the final decision maker
12
13. Team Roles
Implementer Project Manager
– Identifying & managing project throttle points
– Developing Project & Sub-Project schedules
– Analyzing impact of change
– Managing RAAID management
– Prioritizing & burning down issues
– Coordinating of all contractor efforts
13
14. Team Roles
Technical Liaison
– Managing on-site & off-site developers
– Translating development activities into terms
of business impact for the project team
– Attending to application technology changes
– Addressing CEMLI remediation
– Packaging code for migration
– Identifying & scheduling patches
14
16. Team Roles
Communications Manager
– Setting & communicating user expectations
– Coordinating & scheduling all client efforts
including training, testing & meetings
– Communicating to users the projects’ status
– Assuring users developed & signed-off test
scripts & results
– Managing users complaints & attitude
– Imparting ”What Is In It For Me?” to users
– Identifying users hot-points
– Keeping the client teams fed
16
17. Developing Project Approach
• Starting with the end in mind
– Taking a “Lather, Rinse, Repeat” methodology
– Testing, Testing, Testing
– Scheduling aggressively
• Focusing
– Minimizing & scoping the projects changes
– Sequencing milestones
– Concentrating on throttle-points
17
18. Putting First Things First
• Determining which sub-projects must or could
happen early
• Determining which sub-projects could finish late
• Assessing project & sub-projects dependencies
• Prioritizing sub-projects based on how they merge
into main project
• Aligning overlapping sub-projects for common CRP
– Some sub-projects had independent initial CRPs
18
19. Keeping Projects On Track
• Developing Communication Plans
– Holding daily meeting with the project team
– Reporting statuses weekly to the user community
– Providing monthly reviews to the executive
sponsorship
• Reviewing the project plans
– Sequencing & managing project milestones
– Managing to the throttle points
• Tracking progress
– Prioritizing & reporting issue burn-down
– Managing the budget burn-down & forecasting
19
20. Adapting To Changes
• Managing scope
– Adding only what had to be added
– Being considerate & stingy
• Reviewing project plan
– Vigilant prioritizing, reviewing and re-prioritizing
– Remembering “The Perfect Storm” does happen!!!
– Planning for contingency: Have plan A, B, C ready
• Being flexible
– Expecting surprises – There will be plenty
– Avoiding the Blame Game
– Taking a “Can do, let us work it through” attitude
– Adjusting project processes with mistakes & over time
20
21. Assuring Quality
Building In Quality
• Emphasizing “Lather, Rinse, Repeat” approach
• Developing & reviewing test scripts early
• Testing, Testing, Testing
• Logging & reviewing RAAID by developers
• Reviewing & validating issue remediation by
independent source
• Diligently using version code
• Utilizing existing Change Management processes
21
22. Preparing For Go Live
• “Lather, Rinse, Repeat”
– UAT testing was no different than the CRPs
– UAT went faster than CRPs
– Sign-Off meant readiness of production
• Remembering that there is always more to do
• Determining what is a ‘showstopper’ & when
– What is required at ‘Go Live’?
– What is needed day 30?
– What is needed day 90?
– What can wait for a future phase?
22
23. Measuring Success
• All projects came in on time and on budget
• CFO stated he kept informed but was not involved
• CEO stated that the only update he got on the
project was that the company was live and project
was successful
23
24. Keys To Success
• Having a dedicated Communications Manager
• Adopting a “Lather, Rinse, Repeat” approach
• Having an independent Quality Review of
issues & documented solutions
• Prefixing all emails with the issue number
• Sequencing & managing project milestones
• Managing to the project throttle points
24
26. Other EiS Technologies Sessions
26
April 10 3:30PM- 4:30PM
Hybrid Cloud Integration - Connecting
Taleo Enterprise Edition With E-
Business Suite
PRESENTER(S):
Kyle Lambert
April 11 10:30AM- 11:30PM
Hacks to Increase Social Media Reach
in Taleo Business Edition Recruit
PRESENTER(S):
Suresh Pallapothu
April 11 12:45PM- 1:45PM
Go Mobile! Taleo Mobile Enabled
Websites
PRESENTER(S):
Austin Reason
April 11 2:00PM- 3:00PM
ANN INC- Hiring the Best by Removing
Disparate Data Obstacles
PRESENTER(S):
Manny Fueyo
Marc Ramos
April 12 9:15AM- 10:15AM
Managing Multiple Projects Within E-
Business Suite Upgrade
PRESENTER(S):
Kyle Lambert
April 14 11:00AM- 12:00PM
Oracle Talent Management Cloud: Federal
Implementation Lessons Learned
PRESENTER(S):
John Faucher
Vendor Session
Replacing Discoverer Reports: Quickly. Accurately. Inexpensively PRESENTER(S): Kiran Pasham
27. Managing Multiple Projects Within
E-Business Suite Upgrade
How do you manage multiple simultaneous projects without losing
focus on the key objective or slipping deadlines?
Upgrading E-Business Suite is challenging all by itself.
However, when you need to upgrade your database version, payroll
tax software and sales tax software, while changing hardware
architecture, re-implementing your Receivables implementation and
restructuring your Chart Of Accounts, plus adding launching Manager
Self-Service and an externally accessible employee portal.