The document provides guidance on planning projects using the Oracle Unified Method (OUM), an iterative and incremental approach. It recommends using a layered planning approach with an implementation plan that outlines the overall project roadmap at a high level, and iteration plans that define the objectives and tasks for individual iterations. The key aspects of planning covered include compiling the implementation plan, determining the number of iterations, iteration planning activities like establishing objectives and deliverables, assigning resources and estimating, and identifying dependencies. The guidance emphasizes that planning is an ongoing process and plans will need to evolve as the project progresses through iterations.
The document provides an overview of Oracle's Unified Method (OUM), which is Oracle's standards-based method for deploying Oracle-based business solutions across the entire IT lifecycle. OUM includes project phases, processes, and activities to manage projects in a flexible, scalable, and iterative manner. It balances agility and discipline and leverages industry standards like the Unified Process.
The document provides an overview of the Oracle Unified Method (OUM), Oracle's standards-based method for developing and implementing Oracle-based business solutions across the entire enterprise IT lifecycle. OUM is based on the Unified Software Development Process and uses an iterative and incremental approach. It provides a flexible yet scalable framework to balance agility and discipline on projects. The benefits of using OUM include more focused efforts through clear scoping and architectural models, built-in flexibility to apply to different types of projects, and time savings by leveraging experience captured in the methodology.
This plan provides any parties interested in implementing Oracle Applications with a framework for doing so. It contains the detailed tasks involved and lists the associated resources that may be needed. The Work Breakdown Structure (WBS) codes tie back in to the Oracle AIM documents that should be prepared for each task and phase.
The document discusses the period close and reconciliation process in Oracle R12. It covers the general close steps and specific close checklists for payables, receivables, assets, cash management, and the general ledger. It also discusses intercompany reconciliation and provides resources for period close. Key changes in R12 include new balancing lines and journals to streamline the close process.
This document provides an overview and user guide for Oracle Process Manufacturing Cost Management. It describes how to set up and use standard, actual, and lot costing methods. The document also covers period-end cost processing, copying costs between periods and organizations, and available cost management reports.
The document describes Plan to Produce, Oracle's supply chain management solution. It discusses the key processes involved - planning production based on sales and forecasts, scheduling production, and optimizing manufacturing operations. Oracle Supply Chain Planning Cloud, Manufacturing Cloud, and Manufacturing Intelligence solutions help maximize throughput, increase utilization of resources, and provide visibility and analytics across the supply chain. Case studies show how customers streamlined processes, improved reporting and cash flow, reduced wastage and saved time through automation.
This document provides an overview of the differences between Oracle's legacy Application Implementation Method (AIM) and the new Oracle Unified Method (OUM). Key differences include:
- OUM has 5 phases compared to AIM's 6 phases.
- OUM has 14 processes compared to AIM's 12 processes.
- OUM uses a more flexible, curved process spread between phases compared to AIM's straight process spread.
- OUM provides standardized phase entry/exit milestones, while AIM did not have consistent checkpoints.
- OUM uses a simplified template coding structure of AN, DS, and IM compared to AIM's various complex codes.
The document aims
This document maps documents from the older Application Implementation Methodology (AIM) to documents in the newer Oracle Unified Methodology (OUM). It provides the OUM document name, phase introduced, and whether it is used for customizations or is mandatory/optional for each equivalent AIM document. This mapping can help those using AIM transition to implementing Oracle applications using OUM. The complete listing of mapped documents is available to Oracle Partners on the Oracle Partner website.
The document provides an overview of Oracle's Unified Method (OUM), which is Oracle's standards-based method for deploying Oracle-based business solutions across the entire IT lifecycle. OUM includes project phases, processes, and activities to manage projects in a flexible, scalable, and iterative manner. It balances agility and discipline and leverages industry standards like the Unified Process.
The document provides an overview of the Oracle Unified Method (OUM), Oracle's standards-based method for developing and implementing Oracle-based business solutions across the entire enterprise IT lifecycle. OUM is based on the Unified Software Development Process and uses an iterative and incremental approach. It provides a flexible yet scalable framework to balance agility and discipline on projects. The benefits of using OUM include more focused efforts through clear scoping and architectural models, built-in flexibility to apply to different types of projects, and time savings by leveraging experience captured in the methodology.
This plan provides any parties interested in implementing Oracle Applications with a framework for doing so. It contains the detailed tasks involved and lists the associated resources that may be needed. The Work Breakdown Structure (WBS) codes tie back in to the Oracle AIM documents that should be prepared for each task and phase.
The document discusses the period close and reconciliation process in Oracle R12. It covers the general close steps and specific close checklists for payables, receivables, assets, cash management, and the general ledger. It also discusses intercompany reconciliation and provides resources for period close. Key changes in R12 include new balancing lines and journals to streamline the close process.
This document provides an overview and user guide for Oracle Process Manufacturing Cost Management. It describes how to set up and use standard, actual, and lot costing methods. The document also covers period-end cost processing, copying costs between periods and organizations, and available cost management reports.
The document describes Plan to Produce, Oracle's supply chain management solution. It discusses the key processes involved - planning production based on sales and forecasts, scheduling production, and optimizing manufacturing operations. Oracle Supply Chain Planning Cloud, Manufacturing Cloud, and Manufacturing Intelligence solutions help maximize throughput, increase utilization of resources, and provide visibility and analytics across the supply chain. Case studies show how customers streamlined processes, improved reporting and cash flow, reduced wastage and saved time through automation.
This document provides an overview of the differences between Oracle's legacy Application Implementation Method (AIM) and the new Oracle Unified Method (OUM). Key differences include:
- OUM has 5 phases compared to AIM's 6 phases.
- OUM has 14 processes compared to AIM's 12 processes.
- OUM uses a more flexible, curved process spread between phases compared to AIM's straight process spread.
- OUM provides standardized phase entry/exit milestones, while AIM did not have consistent checkpoints.
- OUM uses a simplified template coding structure of AN, DS, and IM compared to AIM's various complex codes.
The document aims
This document maps documents from the older Application Implementation Methodology (AIM) to documents in the newer Oracle Unified Methodology (OUM). It provides the OUM document name, phase introduced, and whether it is used for customizations or is mandatory/optional for each equivalent AIM document. This mapping can help those using AIM transition to implementing Oracle applications using OUM. The complete listing of mapped documents is available to Oracle Partners on the Oracle Partner website.
The document describes the process flows for procurement agreements in Oracle Fusion, including Blanket Purchase Agreements (BPA) and Contract Purchase Agreements (CPA). It explains how to create a BPA by entering supplier, item, and pricing details. It also explains how to reference a BPA when creating a purchase order to apply the agreed upon pricing. The document provides screenshots to illustrate creating a CPA, which does not require item lines, and differences in controls compared to a BPA. It also briefly mentions additional procurement agreement capabilities like importing agreements, retroactive price updates, and generating approved supplier lists.
This document proposes Tech Mahindra's solution for Genpact's Oracle ERP implementation. It includes:
1) An introduction of the Tech Mahindra team leading the implementation.
2) A hybrid "big bang" and phased approach is proposed - the payroll and HRMS instances will undergo a technical upgrade together, while the BPM rollout will be done in phases by geography.
3) The scope of work includes upgrading the payroll and HRMS instances from 11i to R12, reimplementing the BPM and CMIT businesses on the upgraded HRMS instance, and post go-live support.
Oracle Process Manufacturing enables firms to better manage batch production involving variable ingredients, scalable recipes and flexible routings to satisfy unique specifications typically found in chemicals, food and beverage, life sciences, pharma and natural resources.
Take it to the Oracle ERP Cloud! Hitachi will profile a recent cloud ERP implementation. Hitachi will discuss why Oracle Cloud ERP was selected, the project approach, timeline and lessons learned. Hitachi will also discuss the multiple Oracle cloud solutions (Sales Cloud, Marketing Cloud, HCM Cloud, etc.) they have already deployed in-house to support their own business growth.
Simplify Complex Consolidations and Close Processes with Oracle Financial Con...Alithya
Oracle Financial Consolidation and Close Cloud Service (FCCS) mixes best practices with customization to streamline and enhance the close and consolidation process. This configurable product leverages out-of-the-box content which gives companies the framework needed to deploy an easy-to-use, yet sophisticated, close solution. It requires no infrastructure investments, offers flexible deployment options, and provides fast time-to-value.
In this presentation, we explore the full range of capabilities of this solution, including the orchestration of the close process, supplemental data collection, ease of administration, and more. Find out how FCCS can be used to address the complexities that are encountered with consolidations, such as foreign currency translation, intercompany eliminations, and ownership requirements. We touch on additional features that are improved in the cloud such as process automation, administration, and supplemental data collection. Interact and ask questions to learn more about this world-class solution for close and consolidation applications and decide if it's time for you to make the move to the Cloud!
This document provides instructions for setting up Oracle Enterprise Asset Management (eAM) including defining organizations, enabling organizations for eAM, setting up eAM parameters, reviewing installed base parameters, defining areas, departments, resources, activity types, causes, priorities, and criticality codes. The setup covers core eAM definitions required to perform asset management tasks within Oracle eAM.
Before Oracle's multi-org structure, each business unit required a separate Oracle instance. Multi-org allows multiple operating units and their relationships to be defined within a single Oracle installation, keeping each unit's data separate. It logically partitions application data by operating unit for security. Key components include the business group (highest level), set of books for accounting, legal entities, operating units for transactions, and inventory organizations for inventory data.
This document provides demonstrations for configuring subledger accounting in Oracle Applications R12. It begins with creating responsibilities and users, then demonstrates how to copy an existing accounting method and validate an application accounting definition. Later demos show how to create new journal line types, descriptions, derivation rules, line definitions, and a full accounting method from scratch. The document provides detailed steps and screenshots to guide the reader through each configuration task.
This document provides usage terms and conditions for Oracle's online training materials. It states that Oracle business partners can download and copy materials for internal employee training only, and cannot resell, redistribute, or create derivatives. Oracle disclaims all warranties and liability for damages from using the materials. Partners must agree to indemnify Oracle from any legal actions resulting from their use of the materials. The document also provides purposes and disclaimers for the information contained.
OKE is an acronym for Oracle Project Contracts which is a tool for contract creation, execution, and management that links contracts and documents in Documentum. It provides benefits like consistent contract processes, real-time access to contract data, and enhanced reporting capabilities. The document discusses how OKE integrates with other Oracle systems like Project Accounting, Purchasing, and Payables to track changes to project budgets, commitments, forecasts, and actual costs through the contract, PO, invoicing, and change order processes.
Introducing Oracle Advanced Financial Controls Cloud ServiceDane Roberts
This #OOW16 session featured three panelists, Mark Stebelton, Director of Product Management for Oracle’s Risk Management Cloud Services, Kent Spaulding Oracle Software Architect and Stephen D’Arcy, Director PwC. This session included a screenshot demonstration of Oracle’s latest Cloud Services - Advanced Financial Controls - for automating transaction monitoring; discussion of the underlying, award winning analytical engine; panelist Q&A that highlighted high-value use cases, key metrics, thought leadership and anecdotal lesions learned from clients that utilize transaction monitoring.
The document provides an overview of the Oracle AIM (Application Implementation Methodology) framework. It describes AIM as a methodology for implementing Oracle applications that defines the tasks, order, and resources needed for a project. The document outlines the key phases and processes of an AIM project, including definitions, operations analysis, solution design, build, transition, and production. It also describes the 12 processes that are part of AIM, such as project management, business requirements definition, and module design and build.
#OOW16 - Introduction to Advanced Access ControlsDane Roberts
Get your first look at our upcoming cloud service to continually detect and manage unwanted user access in Oracle ERP, HCM & SCM Clouds - e.g., separation of duties (SoD) and access to sensitive data and functionality. Learn about application security and control best practices from KPMG's Director of Advisory Services, Nick Seeman, and Service Corporation International's Chief Audit Executive, Katrina Johnson. Get insight into using this new cloud service to streamline ERP/HCM/SCM role design and access policies, and improve access controls for Sarbanes Oxley (SOX) and comparable regulations from Oracle Product Development's Mark Stebelton and Barry Greenhut.
Moving from MaxL to EPMAutomate for Oracle Planning & Budgeting Cloud Service...mindstremanalysis
MindStream Analytics is a leading consulting and managed services provider with a proven track record for helping leading global companies address their enterprise challenges, focused on delivering sustainable profitability and competitive advantage. Data is a new economic as set that is rapidly expanding and changing. You're challenged to figure out how to use it to your organization's advantage.
We work collaboratively with our clients and bringing innovative strategies that enable organizations to gain competitive edge and win with data.
The document provides an introduction to Oracle Financials. It discusses that the job is to implement Oracle Financials modules according to a client's business requirements. It then gives an overview of Oracle Financials modules, including Payables, Receivables, Cash Management, Assets, and General Ledger.
Fusion applications gl and ar suresh c-mishraSuresh Mishra
Fusion Applications is Oracle's next-generation suite of integrated applications currently in development. It combines capabilities from Oracle's existing product portfolio with a new rich user interface and embedded analytics. Key areas covered in version 1.0 include financial management, human capital management, sales and marketing management, supply chain management, and project portfolio management. The document provides details on the new user interface, functionality in various modules like general ledger and accounts receivable, and enhanced setup and transaction processes in Fusion Applications.
Oracle General Ledger allows users to create mass allocation journals to distribute expenses and revenues across cost centers, departments, and divisions. This is done by creating mass allocation definitions that include allocation formulas with parameters to specify how amounts will be distributed. The allocation formulas use a cost pool multiplied by a usage factor divided by a total usage to calculate allocation amounts. Users can generate allocation journals using either a full or incremental allocation method and must validate the allocation definitions and formulas before generating journals to distribute amounts according to the formulas.
OOW16 - Oracle E-Business Suite Integration Best Practices [CON6709]vasuballa
Oracle is investing across applications and technologies to make the application integration experience easier for customers. Oracle E-Business Suite provides tools and technologies to address various application integration challenges and styles. Learn more about Oracle’s integration offering for cloud, data, event-driven, business-to-business, and process-centric integrations. In this session, you will get a better understanding of what Oracle integration technologies you can use and how, when, and where you can leverage them to connect end-to-end business processes across your enterprise, including the Oracle Applications portfolio in the cloud.
The document discusses Agile software development methodology. Some key points:
- Agile emphasizes incremental delivery of functionality in short cycles (1-6 weeks called sprints) allowing for adaptation to changing priorities.
- Each sprint includes all tasks needed to deliver new features. Teams are self-organizing and cross-functional.
- Common agile roles include Scrum Master, developers, testers. Scrum Masters facilitate communication and remove impediments.
- The agile process involves sprint planning, daily stand-ups, and final demos at the end of each sprint to accept completed work.
The document outlines an agenda for training on Oracle inventory management. It will cover introduction to Oracle inventory, enterprise structure, setup, creating and maintaining items, controls, transactions, accuracy, and planning. Key concepts that will be discussed include inventory definitions, organization calendars, categories, transactions, and material and business flows.
The document describes the process flows for procurement agreements in Oracle Fusion, including Blanket Purchase Agreements (BPA) and Contract Purchase Agreements (CPA). It explains how to create a BPA by entering supplier, item, and pricing details. It also explains how to reference a BPA when creating a purchase order to apply the agreed upon pricing. The document provides screenshots to illustrate creating a CPA, which does not require item lines, and differences in controls compared to a BPA. It also briefly mentions additional procurement agreement capabilities like importing agreements, retroactive price updates, and generating approved supplier lists.
This document proposes Tech Mahindra's solution for Genpact's Oracle ERP implementation. It includes:
1) An introduction of the Tech Mahindra team leading the implementation.
2) A hybrid "big bang" and phased approach is proposed - the payroll and HRMS instances will undergo a technical upgrade together, while the BPM rollout will be done in phases by geography.
3) The scope of work includes upgrading the payroll and HRMS instances from 11i to R12, reimplementing the BPM and CMIT businesses on the upgraded HRMS instance, and post go-live support.
Oracle Process Manufacturing enables firms to better manage batch production involving variable ingredients, scalable recipes and flexible routings to satisfy unique specifications typically found in chemicals, food and beverage, life sciences, pharma and natural resources.
Take it to the Oracle ERP Cloud! Hitachi will profile a recent cloud ERP implementation. Hitachi will discuss why Oracle Cloud ERP was selected, the project approach, timeline and lessons learned. Hitachi will also discuss the multiple Oracle cloud solutions (Sales Cloud, Marketing Cloud, HCM Cloud, etc.) they have already deployed in-house to support their own business growth.
Simplify Complex Consolidations and Close Processes with Oracle Financial Con...Alithya
Oracle Financial Consolidation and Close Cloud Service (FCCS) mixes best practices with customization to streamline and enhance the close and consolidation process. This configurable product leverages out-of-the-box content which gives companies the framework needed to deploy an easy-to-use, yet sophisticated, close solution. It requires no infrastructure investments, offers flexible deployment options, and provides fast time-to-value.
In this presentation, we explore the full range of capabilities of this solution, including the orchestration of the close process, supplemental data collection, ease of administration, and more. Find out how FCCS can be used to address the complexities that are encountered with consolidations, such as foreign currency translation, intercompany eliminations, and ownership requirements. We touch on additional features that are improved in the cloud such as process automation, administration, and supplemental data collection. Interact and ask questions to learn more about this world-class solution for close and consolidation applications and decide if it's time for you to make the move to the Cloud!
This document provides instructions for setting up Oracle Enterprise Asset Management (eAM) including defining organizations, enabling organizations for eAM, setting up eAM parameters, reviewing installed base parameters, defining areas, departments, resources, activity types, causes, priorities, and criticality codes. The setup covers core eAM definitions required to perform asset management tasks within Oracle eAM.
Before Oracle's multi-org structure, each business unit required a separate Oracle instance. Multi-org allows multiple operating units and their relationships to be defined within a single Oracle installation, keeping each unit's data separate. It logically partitions application data by operating unit for security. Key components include the business group (highest level), set of books for accounting, legal entities, operating units for transactions, and inventory organizations for inventory data.
This document provides demonstrations for configuring subledger accounting in Oracle Applications R12. It begins with creating responsibilities and users, then demonstrates how to copy an existing accounting method and validate an application accounting definition. Later demos show how to create new journal line types, descriptions, derivation rules, line definitions, and a full accounting method from scratch. The document provides detailed steps and screenshots to guide the reader through each configuration task.
This document provides usage terms and conditions for Oracle's online training materials. It states that Oracle business partners can download and copy materials for internal employee training only, and cannot resell, redistribute, or create derivatives. Oracle disclaims all warranties and liability for damages from using the materials. Partners must agree to indemnify Oracle from any legal actions resulting from their use of the materials. The document also provides purposes and disclaimers for the information contained.
OKE is an acronym for Oracle Project Contracts which is a tool for contract creation, execution, and management that links contracts and documents in Documentum. It provides benefits like consistent contract processes, real-time access to contract data, and enhanced reporting capabilities. The document discusses how OKE integrates with other Oracle systems like Project Accounting, Purchasing, and Payables to track changes to project budgets, commitments, forecasts, and actual costs through the contract, PO, invoicing, and change order processes.
Introducing Oracle Advanced Financial Controls Cloud ServiceDane Roberts
This #OOW16 session featured three panelists, Mark Stebelton, Director of Product Management for Oracle’s Risk Management Cloud Services, Kent Spaulding Oracle Software Architect and Stephen D’Arcy, Director PwC. This session included a screenshot demonstration of Oracle’s latest Cloud Services - Advanced Financial Controls - for automating transaction monitoring; discussion of the underlying, award winning analytical engine; panelist Q&A that highlighted high-value use cases, key metrics, thought leadership and anecdotal lesions learned from clients that utilize transaction monitoring.
The document provides an overview of the Oracle AIM (Application Implementation Methodology) framework. It describes AIM as a methodology for implementing Oracle applications that defines the tasks, order, and resources needed for a project. The document outlines the key phases and processes of an AIM project, including definitions, operations analysis, solution design, build, transition, and production. It also describes the 12 processes that are part of AIM, such as project management, business requirements definition, and module design and build.
#OOW16 - Introduction to Advanced Access ControlsDane Roberts
Get your first look at our upcoming cloud service to continually detect and manage unwanted user access in Oracle ERP, HCM & SCM Clouds - e.g., separation of duties (SoD) and access to sensitive data and functionality. Learn about application security and control best practices from KPMG's Director of Advisory Services, Nick Seeman, and Service Corporation International's Chief Audit Executive, Katrina Johnson. Get insight into using this new cloud service to streamline ERP/HCM/SCM role design and access policies, and improve access controls for Sarbanes Oxley (SOX) and comparable regulations from Oracle Product Development's Mark Stebelton and Barry Greenhut.
Moving from MaxL to EPMAutomate for Oracle Planning & Budgeting Cloud Service...mindstremanalysis
MindStream Analytics is a leading consulting and managed services provider with a proven track record for helping leading global companies address their enterprise challenges, focused on delivering sustainable profitability and competitive advantage. Data is a new economic as set that is rapidly expanding and changing. You're challenged to figure out how to use it to your organization's advantage.
We work collaboratively with our clients and bringing innovative strategies that enable organizations to gain competitive edge and win with data.
The document provides an introduction to Oracle Financials. It discusses that the job is to implement Oracle Financials modules according to a client's business requirements. It then gives an overview of Oracle Financials modules, including Payables, Receivables, Cash Management, Assets, and General Ledger.
Fusion applications gl and ar suresh c-mishraSuresh Mishra
Fusion Applications is Oracle's next-generation suite of integrated applications currently in development. It combines capabilities from Oracle's existing product portfolio with a new rich user interface and embedded analytics. Key areas covered in version 1.0 include financial management, human capital management, sales and marketing management, supply chain management, and project portfolio management. The document provides details on the new user interface, functionality in various modules like general ledger and accounts receivable, and enhanced setup and transaction processes in Fusion Applications.
Oracle General Ledger allows users to create mass allocation journals to distribute expenses and revenues across cost centers, departments, and divisions. This is done by creating mass allocation definitions that include allocation formulas with parameters to specify how amounts will be distributed. The allocation formulas use a cost pool multiplied by a usage factor divided by a total usage to calculate allocation amounts. Users can generate allocation journals using either a full or incremental allocation method and must validate the allocation definitions and formulas before generating journals to distribute amounts according to the formulas.
OOW16 - Oracle E-Business Suite Integration Best Practices [CON6709]vasuballa
Oracle is investing across applications and technologies to make the application integration experience easier for customers. Oracle E-Business Suite provides tools and technologies to address various application integration challenges and styles. Learn more about Oracle’s integration offering for cloud, data, event-driven, business-to-business, and process-centric integrations. In this session, you will get a better understanding of what Oracle integration technologies you can use and how, when, and where you can leverage them to connect end-to-end business processes across your enterprise, including the Oracle Applications portfolio in the cloud.
The document discusses Agile software development methodology. Some key points:
- Agile emphasizes incremental delivery of functionality in short cycles (1-6 weeks called sprints) allowing for adaptation to changing priorities.
- Each sprint includes all tasks needed to deliver new features. Teams are self-organizing and cross-functional.
- Common agile roles include Scrum Master, developers, testers. Scrum Masters facilitate communication and remove impediments.
- The agile process involves sprint planning, daily stand-ups, and final demos at the end of each sprint to accept completed work.
The document outlines an agenda for training on Oracle inventory management. It will cover introduction to Oracle inventory, enterprise structure, setup, creating and maintaining items, controls, transactions, accuracy, and planning. Key concepts that will be discussed include inventory definitions, organization calendars, categories, transactions, and material and business flows.
1) The document describes a project to design and test a tower made of popsicle sticks to understand how skeletal structures transfer loads efficiently.
2) The objective is to build a tower that is at least 30cm tall using no more than 100 popsicle sticks and that can support the greatest amount of weight.
3) After several attempts, the group created a tower with 76 sticks that was 33cm tall and could support up to 50kg before breaking, resulting in an efficiency rating of 18.13.
The document discusses God punishing individuals and groups. It prompts the reader to discuss who may feel God's wrath and why with others. It also references a poem by Langston Hughes called "I, too sing America" that celebrates African Americans' citizenship and freedom in the United States.
The document discusses installing a blog extension in Magento. It describes how the blog extension allows merchants to communicate with customers, provide store news/updates, and build engagement/sales. The extension installation process involves copying the extension key, accessing the Magento Connect Manager, and installing. Key features of the extension include RSS integration, multistore support, WYSIWYG editing, and tagging/comments.
Android notifications allow apps to display messages in the notification bar even when the app is not open. Notifications can include actions that trigger intents when selected. Common scenarios for actions include accepting/rejecting meetings or liking/sharing social media posts. Notifications can be expanded to include additional details like images or multiple lines of text. Custom notifications allow more complex interfaces with elements like buttons or charts.
iOS 3D Touch available in new iPhone 6S and 6S Plus,
Truly futuristic User Experience, Not only time saver but improves productivity too. Of course more productivity means more time and money for you and your customers. Let's Connect over an email and together build your next big thing Mobile App Arena.
Are you looking for somebody to take care of your children or elderly parents, or fed up with the negligence of your ward by their current daycare center/ old age homes, then we can help you! Rent-a-Parent services by us is surely the ideal choice as compared to our competitors, the day care centers, child care centers or old folks home whereby we provide personalized care by our experienced and well trained employees. Moreover, these competitors usually many people to be looked after and attended unlike us. If the customer would like to request for somebody to look after their child during the odd hours, only we could provide such a service. Furthermore, if elderly people need care and affection, they also can approach us. This is a much better choice compared to the old age homes because, they will be in their own comfortable surrounding. In order to turn this service into something promising there are some things that can be done by those providing this services.
The document introduces Eddystone, an open Bluetooth low energy (BLE) beacon format developed by Google. It discusses how Eddystone aims to address real-life use cases, support multiple platforms, and ensure security and privacy. It also describes the various Eddystone frame types and how the format supports better context for apps and easier management of beacon fleets for businesses. Finally, it provides examples of how Google products will utilize Eddystone beacons.
This document describes a program called "Students as Teachers" developed at a middle school in New Jersey to help English Language Learners succeed in science. The program is based on the ideas that students learn best in groups and when they can leverage their strengths. It has students of varying English proficiency levels work collaboratively in groups to summarize, illustrate, and teach each other content from science chapters. The teacher introduces topics and monitors the process, while students assume responsibilities within their roles. Evaluation found the program improved students' science grades by a letter on average and reduced disciplinary issues, as students focused more deeply on language proficiency when explaining concepts to peers. The conclusion is that allowing collaborative work and student-created materials can help many English
A fractographic study on toughening of epoxy resin using ground tyre rubberFernanda Souza
This document describes a study that examined the fracture surfaces of epoxy resin modified with ground tire rubber to investigate toughening mechanisms. Five surface treatment techniques were used to improve compatibility between the rubber particles and epoxy matrix, including two silane coupling agents, oxygen plasma, acrylic acid, and a mixture of acrylic acid and benzoylperoxide. Fracture toughness tests found the treatments increased toughness by improving the interface, leading to crack deflection as the main toughening mechanism. Secondary mechanisms included shear deformation and some debonding initiated at the interface, as shown by fractographic analysis of the fracture surfaces.
The document provides an overview of the Oracle Unified Method (OUM), Oracle's standards-based method for deploying Oracle-based business solutions across the entire IT lifecycle. OUM uses a project framework with phases and processes to coordinate activities and provide quality checkpoints. It includes flexible, scalable views and tailors the appropriate activities and tasks for each project. The key features that enable this are its flexibility, scalability, and use of different views.
This white paper covers a new approach to tracking project performance which identifies variance gaps between the baseline plan and actual performance for the project as a whole as well as specific deliverables, contractors, locations, or any other group of activities.
The document discusses various communication tools used to manage project time, including introducing the baseline schedule, change control plan, change requests, Gantt charts, logic network diagrams, project milestone lists, project scheduling tools, and schedule management plans. It provides details on each tool, how project managers can use them to communicate with stakeholders, and the benefits they provide for time management and tracking project progress.
This document discusses project implementation and provides guidance on planning and tracking a project implementation plan. It begins by defining project implementation as putting plans and visions into action. It then lists the purposes of implementation as putting the action plan into operation, delivering results to achieve objectives, managing resources efficiently, and monitoring and reporting progress. Several key steps for implementation planning are outlined, including creating a list of required outcomes, allocating champions for each outcome, determining necessary actions, establishing roles and accountability, setting up a tracking sheet, following a project management methodology, and scheduling reviews. Common project implementation tracking methods like Gantt charts, critical path methods, and PERT charts are also summarized.
The document summarizes the typical project life cycle process used by project managers. It consists of 5 phases: (1) initiating, (2) planning, (3) executing, (4) monitoring/controlling, and (5) closing. Each phase involves certain key activities and defines the stages a project goes through from start to finish. Following a structured life cycle framework helps ensure projects are completed on time and on budget.
This document provides a minor project report on project monitoring and controlling using Microsoft Project. It includes an introduction discussing project management processes like initiation, planning, execution, monitoring and controlling. It also includes a literature review on the history of project management and critical studies. The objectives are to govern project operations, understand and control schedules and finances, communicate project information, and ensure projects are completed on schedule. The methodology discusses techniques like critical path method, project evaluation and review technique, and Gantt charts.
Now-a-days whole world facing competition in every fields, including construction industry. Large construction companies carry out big projects, according to the need of that project, they uses different methods of construction and management. Critical Path Method (CPM), Linear Scheduling Method (LSM), and Line Of Balance (LOB) are the different methods of construction project management. All the construction companies utilize these methods according their utilities and requirement of project. In this report, Line of balance method is explained with its different component on the basis of some related works discussed different alternatives and strategies to sequence activities in the long run. This report contains a study carried out in a construction company in which LOB concept is used in the initial planning phase of a high-rise residential project. Based on the information provided by different LOBs, representing different scenarios, It is further discussed with projects managers, superintendents, and crews the advantages and disadvantages of each scenario regarding the project’s lead time, activities cycle time, gang sizes, batch sizes, buffers, sequencing and interferences between activities .
The document outlines a technical project monitoring framework for projects funded by the National ICT R&D Fund. It describes the key aspects of project monitoring including regular project reporting, a Project Review Committee to conduct mid-project reviews, and guidelines for project management, task management, change management, risk management, and project closure. Task management involves task scheduling using techniques like precedence diagrams, critical path method, and Gantt charts. Approved open source systems for task tracking are also listed.
Improving DOE Project Performance Using the DOD Integrated Master PlanGlen Alleman
DOE O 413 measures a project’s progress to plan by the consumption of funding, the passage of time, and the meeting of milestones. In March of 2003, then Under Secretary, Energy, Science, Card received a memo directing the implementation of Project Management and the Project Management Manual, including the Integrated Master Plan and Integrated Master Schedule. This directive states “the integrated master plan and schedule tie together all project tasks by showing their logical relationships and any constraints controlling the start or finish of each task. This process results in a hierarchy of related functional and layered schedules derived from the Work Breakdown Structure that can be used for monitoring and controlling project progress.” This paper shows how restoring the IMP/IMS paradigm to DOE program management increases the probability of program success in ways not currently available using DOD O 413 processes alone.
Project management involves planning, organizing, and managing resources to achieve specific goals within constraints like scope, time, and budget. A project has a defined start and end, unlike ongoing operations. There are typically four phases of a construction project: concept, planning, execution, and transfer. The planning and engineering phases are when the project is designed on paper before physical implementation. Project management requires balancing work during execution while preparing for completion.
The document provides an overview of Oracle's Unified Method (OUM), which is Oracle's standards-based method for deploying Oracle-based business solutions across the entire IT lifecycle. OUM includes project phases, processes, and activities to manage projects in a flexible, scalable, and iterative manner. It balances agility and discipline and leverages industry standards like the Unified Process.
This document provides an overview of project management tools and techniques. It discusses the phases of project management, including initiating, planning, executing, and closing. For the planning phase, it describes key activities like developing a work breakdown structure, estimating resources and costs, creating schedules, and developing communication plans. It also covers tools for planning like Gantt charts, PERT diagrams, and critical path scheduling. The document provides details on tasks, activities, and procedures for each phase of managing a project.
This document discusses planning processes for iterative software projects. It covers work breakdown structures, planning guidelines, cost and schedule estimating, and the iteration planning process. Some key points:
- Work breakdown structures (WBS) should be organized around workflows and evolve over the project life cycle to accommodate changes.
- Planning guidelines provide default budgets for first-level WBS elements and distributions of effort and schedule across project phases.
- Cost and schedule estimates should use both top-down macro analysis and bottom-up micro analysis to converge on accurate plans.
- Most projects will have between 4-9 iterations, typically with 1 inception, 2 elaboration, 2 construction, and 1 transition iteration.
- Effective
The document discusses planning a software project. It covers key tasks in project planning including effort estimation, scheduling, quality planning, and risk management. Effective project planning is important to predictably deliver projects on time and on budget by properly estimating effort, creating a schedule, and managing risks and quality.
Quite often, we see MS Project schedules getting written but quickly consigned to cold storage with project running in a loosely monitored fashion. Why does this happen? This presentation answers this question by highlighting problems with ineffective schedules and provides guidelines to write effective schedules.
Improving Project Performance in the DOEGlen Alleman
- The document discusses improving project performance at the US Department of Energy (DOE) by adopting aspects of the integrated master plan (IMP) and integrated master schedule (IMS) processes used by the US Department of Defense (DOD).
- The DOD IMP/IMS approach measures progress through increasing maturity of project outcomes and deliverables, rather than just cost and schedule performance. This provides better visibility into a project's effectiveness for customers.
- Adopting an event-based planning approach like the DOD's IMP, with accomplishments and criteria to measure maturity, would improve the probability of success for DOE projects.
This document discusses software project scheduling. It defines software project scheduling as distributing estimated effort across a planned project duration by allocating effort to specific software engineering tasks. The objective is to create a set of engineering tasks that will enable completing the project on time. Building large software systems involves many interdependent tasks, making schedules important for understanding, managing, and evaluating project progress. Effective scheduling involves decomposing the project into tasks, establishing interdependencies, allocating time and effort, validating resources, assigning responsibilities, defining outcomes, and associating milestones.
The document discusses key aspects of software project planning including process planning, effort estimation, schedule and resource estimation, and quality planning. It emphasizes that effective project management is important for project success. Project planning aims to create a plan to meet commitments by defining processes, estimating effort, creating a schedule and milestones, and defining quality objectives and risk plans. Estimation models like COCOMO are discussed for estimating effort based on project size and characteristics.
1. The document provides guidance on developing an effective project schedule according to generally accepted good practices. It discusses scheduling roles and responsibilities, the purpose of a project schedule, and planning versus scheduling.
2. Key aspects of designing an effective project schedule that are covered include determining an appropriate level of detail, status update cycle, and time scale for activities. The overall process of developing a project schedule is also outlined.
3. An effective project schedule is a dynamic tool that provides a roadmap for completing project work successfully and allows monitoring of progress to make accurate projections.
Developing project objectives and Execution plan in Economy management Nzar Braim
my aim in creating this report is to discuss about developing project objectives and
execution plan ,In every project and work that is done we have to consider a set of
things because each project must have its own goals and objectives.
It has to have its own time and the project has to be successful in all areas And to
further support the report we put an example on the schedule talks about 150m street
in Erbil.
At first we discuss about execution, next discuss about elements, then discuss
developing project objectives, after that the factors that make the project a success.
QA or the Highway - Component Testing: Bridging the gap between frontend appl...zjhamm304
These are the slides for the presentation, "Component Testing: Bridging the gap between frontend applications" that was presented at QA or the Highway 2024 in Columbus, OH by Zachary Hamm.
inQuba Webinar Mastering Customer Journey Management with Dr Graham HillLizaNolte
HERE IS YOUR WEBINAR CONTENT! 'Mastering Customer Journey Management with Dr. Graham Hill'. We hope you find the webinar recording both insightful and enjoyable.
In this webinar, we explored essential aspects of Customer Journey Management and personalization. Here’s a summary of the key insights and topics discussed:
Key Takeaways:
Understanding the Customer Journey: Dr. Hill emphasized the importance of mapping and understanding the complete customer journey to identify touchpoints and opportunities for improvement.
Personalization Strategies: We discussed how to leverage data and insights to create personalized experiences that resonate with customers.
Technology Integration: Insights were shared on how inQuba’s advanced technology can streamline customer interactions and drive operational efficiency.
ScyllaDB is making a major architecture shift. We’re moving from vNode replication to tablets – fragments of tables that are distributed independently, enabling dynamic data distribution and extreme elasticity. In this keynote, ScyllaDB co-founder and CTO Avi Kivity explains the reason for this shift, provides a look at the implementation and roadmap, and shares how this shift benefits ScyllaDB users.
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...Jason Yip
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
Lee Barnes - Path to Becoming an Effective Test Automation Engineer.pdfleebarnesutopia
So… you want to become a Test Automation Engineer (or hire and develop one)? While there’s quite a bit of information available about important technical and tool skills to master, there’s not enough discussion around the path to becoming an effective Test Automation Engineer that knows how to add VALUE. In my experience this had led to a proliferation of engineers who are proficient with tools and building frameworks but have skill and knowledge gaps, especially in software testing, that reduce the value they deliver with test automation.
In this talk, Lee will share his lessons learned from over 30 years of working with, and mentoring, hundreds of Test Automation Engineers. Whether you’re looking to get started in test automation or just want to improve your trade, this talk will give you a solid foundation and roadmap for ensuring your test automation efforts continuously add value. This talk is equally valuable for both aspiring Test Automation Engineers and those managing them! All attendees will take away a set of key foundational knowledge and a high-level learning path for leveling up test automation skills and ensuring they add value to their organizations.
Session 1 - Intro to Robotic Process Automation.pdfUiPathCommunity
👉 Check out our full 'Africa Series - Automation Student Developers (EN)' page to register for the full program:
https://bit.ly/Automation_Student_Kickstart
In this session, we shall introduce you to the world of automation, the UiPath Platform, and guide you on how to install and setup UiPath Studio on your Windows PC.
📕 Detailed agenda:
What is RPA? Benefits of RPA?
RPA Applications
The UiPath End-to-End Automation Platform
UiPath Studio CE Installation and Setup
💻 Extra training through UiPath Academy:
Introduction to Automation
UiPath Business Automation Platform
Explore automation development with UiPath Studio
👉 Register here for our upcoming Session 2 on June 20: Introduction to UiPath Studio Fundamentals: https://community.uipath.com/events/details/uipath-lagos-presents-session-2-introduction-to-uipath-studio-fundamentals/
From Natural Language to Structured Solr Queries using LLMsSease
This talk draws on experimentation to enable AI applications with Solr. One important use case is to use AI for better accessibility and discoverability of the data: while User eXperience techniques, lexical search improvements, and data harmonization can take organizations to a good level of accessibility, a structural (or “cognitive” gap) remains between the data user needs and the data producer constraints.
That is where AI – and most importantly, Natural Language Processing and Large Language Model techniques – could make a difference. This natural language, conversational engine could facilitate access and usage of the data leveraging the semantics of any data source.
The objective of the presentation is to propose a technical approach and a way forward to achieve this goal.
The key concept is to enable users to express their search queries in natural language, which the LLM then enriches, interprets, and translates into structured queries based on the Solr index’s metadata.
This approach leverages the LLM’s ability to understand the nuances of natural language and the structure of documents within Apache Solr.
The LLM acts as an intermediary agent, offering a transparent experience to users automatically and potentially uncovering relevant documents that conventional search methods might overlook. The presentation will include the results of this experimental work, lessons learned, best practices, and the scope of future work that should improve the approach and make it production-ready.
Introducing BoxLang : A new JVM language for productivity and modularity!Ortus Solutions, Corp
Just like life, our code must adapt to the ever changing world we live in. From one day coding for the web, to the next for our tablets or APIs or for running serverless applications. Multi-runtime development is the future of coding, the future is to be dynamic. Let us introduce you to BoxLang.
Dynamic. Modular. Productive.
BoxLang redefines development with its dynamic nature, empowering developers to craft expressive and functional code effortlessly. Its modular architecture prioritizes flexibility, allowing for seamless integration into existing ecosystems.
Interoperability at its Core
With 100% interoperability with Java, BoxLang seamlessly bridges the gap between traditional and modern development paradigms, unlocking new possibilities for innovation and collaboration.
Multi-Runtime
From the tiny 2m operating system binary to running on our pure Java web server, CommandBox, Jakarta EE, AWS Lambda, Microsoft Functions, Web Assembly, Android and more. BoxLang has been designed to enhance and adapt according to it's runnable runtime.
The Fusion of Modernity and Tradition
Experience the fusion of modern features inspired by CFML, Node, Ruby, Kotlin, Java, and Clojure, combined with the familiarity of Java bytecode compilation, making BoxLang a language of choice for forward-thinking developers.
Empowering Transition with Transpiler Support
Transitioning from CFML to BoxLang is seamless with our JIT transpiler, facilitating smooth migration and preserving existing code investments.
Unlocking Creativity with IDE Tools
Unleash your creativity with powerful IDE tools tailored for BoxLang, providing an intuitive development experience and streamlining your workflow. Join us as we embark on a journey to redefine JVM development. Welcome to the era of BoxLang.
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
"NATO Hackathon Winner: AI-Powered Drug Search", Taras KlobaFwdays
This is a session that details how PostgreSQL's features and Azure AI Services can be effectively used to significantly enhance the search functionality in any application.
In this session, we'll share insights on how we used PostgreSQL to facilitate precise searches across multiple fields in our mobile application. The techniques include using LIKE and ILIKE operators and integrating a trigram-based search to handle potential misspellings, thereby increasing the search accuracy.
We'll also discuss how the azure_ai extension on PostgreSQL databases in Azure and Azure AI Services were utilized to create vectors from user input, a feature beneficial when users wish to find specific items based on text prompts. While our application's case study involves a drug search, the techniques and principles shared in this session can be adapted to improve search functionality in a wide range of applications. Join us to learn how PostgreSQL and Azure AI can be harnessed to enhance your application's search capability.
QR Secure: A Hybrid Approach Using Machine Learning and Security Validation F...AlexanderRichford
QR Secure: A Hybrid Approach Using Machine Learning and Security Validation Functions to Prevent Interaction with Malicious QR Codes.
Aim of the Study: The goal of this research was to develop a robust hybrid approach for identifying malicious and insecure URLs derived from QR codes, ensuring safe interactions.
This is achieved through:
Machine Learning Model: Predicts the likelihood of a URL being malicious.
Security Validation Functions: Ensures the derived URL has a valid certificate and proper URL format.
This innovative blend of technology aims to enhance cybersecurity measures and protect users from potential threats hidden within QR codes 🖥 🔒
This study was my first introduction to using ML which has shown me the immense potential of ML in creating more secure digital environments!
What is an RPA CoE? Session 2 – CoE RolesDianaGray10
In this session, we will review the players involved in the CoE and how each role impacts opportunities.
Topics covered:
• What roles are essential?
• What place in the automation journey does each role play?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Keywords: AI, Containeres, Kubernetes, Cloud Native
Event Link: https://meine.doag.org/events/cloudland/2024/agenda/#agendaId.4211
"What does it really mean for your system to be available, or how to define w...Fwdays
We will talk about system monitoring from a few different angles. We will start by covering the basics, then discuss SLOs, how to define them, and why understanding the business well is crucial for success in this exercise.
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
The Microsoft 365 Migration Tutorial For Beginner.pptx
Oracle unified method
1. Planning a Project Using the
Oracle Unified Method (OUM) –
An Iterative and Incremental Approach
An Oracle White Paper
February 2011
2. Planning a Project Using the Oracle Unified Method
(OUM)
Executive overview............................................................................................ 3
Introduction........................................................................................................ 3
Planning an OUM Project – A Layered Approach ...................................... 3
Definition of Plans at Each Layer ................................................................... 4
The Implementation Plan ............................................................................ 4
The Iteration Plan ......................................................................................... 4
Planning Using a Top-Down/Bottom-Up Approach ................................. 5
Implementation Planning ................................................................................. 6
Compile the Implementation Plan.............................................................. 7
Factors that Drive the Number of Iterations per Phase ......................... 7
Secure Agreement on the Implementation Plan....................................... 8
Evolve the Implementation Plan ................................................................ 8
Iteration Planning .............................................................................................. 8
Assess the Current State of Project Risks.................................................. 8
Establish the Scope of the Current Iteration ............................................ 8
Objectives of the Current Iteration ....................................................... 8
Team Capacity ........................................................................................... 9
Deliverables for the Iteration ................................................................ 10
Map the Iteration’s Deliverables to OUM Tasks ................................... 10
Assign Resources and Produce Estimates ............................................... 10
Identify Dependencies................................................................................ 11
Establish Success Criteria for the Iteration ............................................. 11
Determine the Assessment Milestones for Each Iteration ................... 11
Compile the Iteration Plan......................................................................... 11
Iteratively Evolve the Plan(s) .................................................................... 11
Considerations for Larger Projects ............................................................... 12
Conclusion ........................................................................................................ 13
References ......................................................................................................... 14
Planning a Project Using the Oracle Unified Method (OUM)
Page 2
3. Planning a Project Using the Oracle Unified Method
(OUM)
EXECUTIVE OVERVIEW
“Life belongs to the living, and he who
lives must be prepared for changes.”
-
Johann Wolfgang von
Goethe
Oracle Unified Method (OUM) uses the Manage Focus Area - Project Management
Method (OUM Manage) to provide a framework in which projects can be planned,
estimated, controlled, and tracked in a consistent manner. OUM is based on the
Unified Process and is therefore both iterative and incremental. The intent of this
white paper is to provide you with a high-level guide for planning an OUM project.
INTRODUCTION
Iterative development using OUM provides many benefits: major risks are
identified and addressed early in the project; requirement changes are identified and
prioritized efficiently; project team utilization is optimized; and progress and quality
are continuously monitored and corrected.
PLANNING AN OUM PROJECT – A LAYERED APPROACH
OUM is designed to be a scalable method that can be applied to any kind of Oracle
project. Plans need to be scalable for different project sizes and complexity and
contain the right level of detail for the current planning horizon. Plans that are too
detailed are almost instantly inaccurate and obscure key objectives. On the other
hand, plans that are too high level will not allow for measurement of project
progress nor keep the project team focused on their day-to-day activities.
Plans need to display the appropriate level of detail and planning horizon for
specific audiences. For example, C-level executives, business area managers and
external stakeholders are rarely interested in the fine details of the project. Their
focus is on the release date, major milestones, business impacts, points at which
major decisions must be made. On the other hand, the project team needs the
details on the lower level plans to plan their daily work and measure progress.
Therefore, a layered approach to planning OUM projects is recommended. As
shown in Figure 1 below, there are two plans active in the project at any given time
on an OUM project – the implementation and the iteration plan.
Planning a Project Using the Oracle Unified Method (OUM)
Page 3
4. One full pass through
all five OUM phases.
Implementation Plan
Iteration
1
Iteration
2
…
Focuses on objectives,
milestones and number
of iterations.
Iteration
N
Covers a single
iteration.
Focuses on achieving
iteration’s objective(s)
and reducing risk.
Figure 1: OUM Planning Layers
DEFINITION OF PLANS AT EACH LAYER
The Implementation Plan
The implementation plan is a brief, coarse-grained outline for the project. The
objectives for the project are reflected in the implementation plan and tie back to
the Business Case developed in the OUM Envision Focus Area. The main purpose
of the implementation plan is to provide a roadmap for achieving the project’s
goals, along with a sketch of the number and purpose of each iteration needed per
phase.
The Iteration Plan
The iteration plan represents the lowest and most detailed layer of planning. An
individual iteration plan will be created for each iteration in the project. The
current iteration plan focuses on how an incremental set of objectives and/or
functionality will be delivered within the framework of the project. The main
purpose of the iteration plan is to lay out how the team will achieve the stated
objectives for the given iteration.
Planning a Project Using the Oracle Unified Method (OUM)
Page 4
5. PLANNING USING A TOP-DOWN/BOTTOM-UP APPROACH
“Agile planning is focused more on the
planning than on the creation of the plan,
encourages change, results in plans that
are easily changed, and is spread
throughout the project.”
-
In OUM, plans are created using a top-down/bottom-up approach in which the
plans at each layer (implementation and iteration) are created and maintained in a
simultaneous fashion. Because the plans are inter-related, it is likely that a change
to a plan at one layer will cause the need for an adjustment to a plan at another
layer. The planning layers are show in Figure 2 below.
Mike Cohn, “Agile
estimating and planning”
(Pearson Education, Inc.)
Project
Inception
Elaboration
Implementation
Plan
Iteration 1
Construction
Iteration 2
Transition
Production
Iteration 3
Task 1
Iteration
Plan
Task 2
Task 3
Increasing
Detail &
Precision
Increasing
Abstraction &
Horizon
Adapted from Kurt Bittner and Ian Spence, “Managing iterative software development projects” (Pearson Education, Inc.)
Figure 2: Top-Down/Bottom Up Planning
The planning starts in the OUM Manage Project Start Up phase where the focus is
on the implementation plan. Also in Project Start Up, the initial iteration of the
OUM Implement Inception phase is drafted to the degree that the project is able to
move into the Inception phase.
During Inception, the implementation plan created in Project Start Up is further
refined as more project requirements and risks are uncovered. As the project
iterates through the later phases, the plans at each layer (implementation and
iteration) will be adjusted based on the results of iteration assessments and as
project objectives shift, as is often the case.
Planning a Project Using the Oracle Unified Method (OUM)
Page 5
6. On any OUM project, an iteration plan for the upcoming iteration is created before
that iteration begins. Also, the implementation plan must be examined to ensure it
is still valid as the iteration plans are created and maintained.
Therefore, at any time on an OUM project the following plans should be active:
•
One implementation plan
•
Two iteration plans – one for the current iteration and a draft for the
upcoming iteration
IMPLEMENTATION PLANNING
In OUM, the implementation plan is an outline of the project, showing the total
number of planned iterations across the five OUM phases (Inception, Elaboration,
Construction, Transition and Production) as well as key milestone dates for each of
these iterations. The implementation plan will sketch out the work across the five
phases by outlining the number of iterations in each phase and major milestones, as
shown in the example in Figure 3 below.
Inception
Elaboration
Elab.
#1
Initial
LO
Construction
Elab.
#2
Constr.
#1
LA
Constr.
#2
Transition
Production
Trans.
#1
Prod.
#1
Constr.
#3
IOC
SP
Figure 3: Example Implementation Plan
Keep in mind, that because OUM utilizes a top-down/bottom-up approach to
planning, the task of developing the implementation plan requires the
implementation plan and current iteration plan to be worked on concurrently.
Planning a Project Using the Oracle Unified Method (OUM)
Page 6
SO
7. Compile the Implementation Plan
The implementation plan presents a roadmap of the planned iterations and should
summarize the following:
•
Objective(s) of each iteration and its contribution to the project goal(s)
•
Business milestones
•
Project commitments
•
Team composition
•
Project dependencies
•
Project approach
Factors that Drive the Number of Iterations per Phase
As part of the implementation planning, the number of iterations per phase will
need to be determined. In general, OUM recommends using the standard number
of iterations as depicted in the OUM Implement Focus Area diagram. However,
there are several factors that can increase or decrease the number of iterations
represented in the plan(s). The factors which would increase the number of
iterations per phase are shown in Table 1 below.
Phase
Factors
Inception
•
Highly variable scope
•
Lack of artifacts from Envision or Envision not
conducted
•
Poorly defined/documented business objectives
•
Disagreement between stakeholders
•
Unstable architecture
•
Unproven architecture
•
Unstable requirements
•
Unavailable development environment
•
Challenging non-functional requirements
•
Large amounts of functionality to develop and test
•
Poor architecture
•
Limited team resources
•
Hardware replacement or rollout
•
Number of deployment and/or rollout sites
•
Large numbers of users to be trained or complex
Elaboration
Construction
Transition
Planning a Project Using the Oracle Unified Method (OUM)
Page 7
8. training required
Production
•
Level and length of support required
•
Incremental rollout strategy
Table 1: Iteration Factors
Secure Agreement on the Implementation Plan
Before commencing work, present the plan to the stakeholders to gain agreement
on the implementation plan. The project team in particular should agree on the
implementation plan.
Evolve the Implementation Plan
Keep in mind that implementation planning, as with the other planning efforts, is
done in an iterative manner. Information will be uncovered during the planning
process that will necessitate amending the implementation plan as well as the
current iteration plan. As the project progresses phase and iteration assessments
will be conducted and feedback will be gained, which will lead to the need to adjust
the plan(s).
ITERATION PLANNING
“This progressive detailing of the project
management plan is often called “rolling
wave planning”, indicating that planning
and documentation is an iterative and
ongoing process.”
-
A Guide to the Project
Management Body of
Knowledge (PMBOK®
Guide) – Fourth Edition
Iteration planning is where the bulk of the planning for a project occurs. Each
iteration should be planned such that a set of specific objectives are accomplished
and a group of project risks are addressed. A project manager will typically analyze
and manage the current iteration plan on a daily basis.
Assess the Current State of Project Risks
Risk management on any project is a dynamic process since project risks will be
eliminated and additional risks will be exposed as the project progresses.
For each iteration, the top risks should be identified based on the current state of
the project (i.e., progress to-date, project phase, team experience, etc.). A rule of
thumb is to narrow the top risks to a list of no more than 10. Based on the list of
the top 10 risks, the iteration plan can be developed to actively address each risk.
Establish the Scope of the Current Iteration
The scope of the iteration will be determined according to the objectives for the
current iteration, team capacity and the iteration’s deliverables. These factors are
discussed in the sections below.
Objectives of the Current Iteration
Based upon the results of the risk analysis and the progress of the project up to this
point must be refined to provide a clear set of measurable and achievable objectives
for the given iteration. The objectives for any iteration should be based on the
current phase the project and should relate to meeting the milestone objectives for
the particular phase.
Planning a Project Using the Oracle Unified Method (OUM)
Page 8
9. Team Capacity
The team’s capacity is a broad measure of the amount of effort the team will be
able to take on in the iteration. The team capacity must be considered when
planning the scope of work for the iteration. The capacity is determined by the
team’s size, availability and velocity, which refers to the speed at which a team can
implement and test use cases and change requests.
As the project progresses, it is often the case that requirements are handled with
less effort which results in an increase in the team’s velocity. Velocity can be used
to develop the initial estimates of the duration and effort required to complete the
current iteration.
A team’s velocity over time can be tracked using a burn-down Chart.
Burn-Down Chart
Remaining
Hours
1200
1000
800
600
400
200
16-out
9-out
2-out
25-set
18-set
11-set
4-set
28-ago
21-ago
14-ago
7-ago
0
Figure 4: Burn-Down Chart
The burn-down chart in Figure 4 above tracks progress by showing a decrease in
the remaining hours. A project team can select any measure they deem relevant to
measure progress such as the number of scenarios completed, days remaining, etc.
The current team’s capacity drives the initial estimates for the effort and duration
for the given iteration. These initial estimates are needed to select which objectives
will be included in the iteration plan and will be further refined as the iteration
planning progresses.
Planning a Project Using the Oracle Unified Method (OUM)
Page 9
10. Deliverables for the Iteration
“You must ensure that the iteration
objectives explicitly address the risks
currently facing the project: the purpose of
an iteration is to mitigate a particular set of
risks.”
-
Kurt Bittner and Ian Spence,
“Managing iterative
software development
projects” (Pearson
Education, Inc.)
.
The deliverables should be associated with one or more of the iteration’s objectives.
The iteration’s deliverables should not be confused with the OUM task work
products. The work products are just a means to an end to producing the
deliverable and are not necessarily related to the project’s objectives.
The most important deliverable of any iteration is the increment that will be
developed. This is defined in OUM by the set of use cases and other nonfunctional requirements that will be achieved during the iteration. These
requirements are selected from the project’s current MoSCoW list. Selecting the
right set of requirements requires collaboration among all team members and
should be focused on the current M’s and S’s shown on the MoSCoW list. Simply
stated, the MoSCoW List registers the known business requirements. Each
requirement is classified by the first letter of: Must, Should, Could or Won’t.
As the project moves along and risks are retired, the focus of the iterations can shift
to filling out the needed functionality for the product under development. Also,
change requests and identified defects can be addressed as the more architecturally
significant use cases have been realized. To achieve the right balance the required
functionality, change requests and defects must be prioritized and estimated by
analyzing the MoSCoW List. See Task RD.045 - Prioritize Requirements for more
information on how MoSCoW is used in OUM.
Map the Iteration’s Deliverables to OUM Tasks
The iteration plan needs lay out the detailed tasks required to achieve the scope that
has been established for the current iteration. This is done by selecting the
appropriate tasks from the OUM WBS for the current phase of the project.
As with any OUM project, it is recommended that the project manager build the
project workplan by starting with the appropriate pre-tailored view for the type of
project under consideration (Solution-Driven Application Implementation,
Requirements-Driven Application Implementation, etc.) and scaling the project for
the given circumstances. The project workplan should focus on the tasks included
in the OUM Implement Core Workflow, which identifies the core tasks within the
Implement Focus Area.
Assign Resources and Produce Estimates
Resources need to be associated with each OUM task included in the iteration plan.
The resources are assigned based on availability and matching the appropriate skillset to the task. All OUM tasks contain a Roles and Responsibilities table that can
be used when assigning resources to tasks. In addition, the Project Roles reference
page provides additional information about the specifics of each role.
Once the resource assignments have been made estimates can be developed for
each task associated with the iteration. The detailed estimates are determined by
refining the initial capacity-based estimates through the use of traditional estimating
techniques that can be augmented through a commitment-driven approach. The
Planning a Project Using the Oracle Unified Method (OUM)
Page 10
11. commitment-driven estimating approach involves asking those team members
assigned to provide an estimate of how much effort will be required to complete
the tasks for each requirement in the iteration.
The individual task estimates balanced with the team velocity form the basis for the
estimates for the iteration plan. These estimates should be verified against broader
estimates completed as part of the initial planning effort for the iteration.
Identify Dependencies
OUM strives to minimize dependencies within the detailed iteration plans due to
the limited duration of the plans. The key to reducing dependencies is to select
relatively independent bits of functionality that can then be integrated to achieve
the iteration’s objectives. However, dependencies cannot be completely eliminated
and must be taken into account. This is where the project manager must work with
the project team and stakeholders to do further analysis of the MoSCoW List. The
dependencies for the use cases addressed in the current iteration must be reflected
on the MoSCoW List must also be reflected in the detailed plan for the iteration.
Establish Success Criteria for the Iteration
Each objective must be associated with an evaluation criterion that defines how the
achievement will be measured and the levels of those measurements that will be
considered a success. These evaluation criteria must be clear and not subjective.
The evaluation criteria must be objective and measurable so that progress toward
the project’s goals can be demonstrated at the end of the iteration.
Determine the Assessment Milestones for Each Iteration
Iteration assessments are essential since iterative development is a collaborative
endeavor between the project team, end users and project sponsors. The iteration
assessments are important events since they uncover potential issues that could
derail the iteration. They also allow the team the ability to take necessary corrective
action to get the project righted. Iteration assessments include demonstrating
evidence of results, open and honest review of the iteration, discussion on how to
improve the next one and acceptance reviews to ensure objectives have been met
and the evaluation criteria have been satisfied.
Compile the Iteration Plan
The iteration plan information should be compiled into a simple document. The
first section of the plan should reflect the scope and objectives of the iteration.
The primary goal of the scope is to make clear the iteration’s objectives, priorities
and evaluation criteria. This information can be used to track the iteration’s
progress and drive the iteration assessment. The rest of the plan captures the
detailed plan for the execution of the iteration.
Iteratively Evolve the Plan(s)
OUM project planning requires the project manager to plan the iteration by
specifying the goals and then allowing the team to determine how best to achieve
Planning a Project Using the Oracle Unified Method (OUM)
Page 11
12. the goals. More information will be brought to light during the execution of an
iteration that will impact the current iteration plan as well as the plan for the next
iteration.
The iteration plan may need to be adjusted to account for a previously unknown
requirement and/or risk. However, it is recommended that rather than re-planning
the current iteration, it is important to keep the team focused on the goal of the
current iteration and remove as many barriers as possible to allow the team to
move forward.
Also, keep in mind that each of the layers – implementation and iteration plans
must be kept in synch. The degree to which an iteration achieves its objectives will
impact future iterations as well as milestones on the implementation plan. As the
phase and iteration assessments are conducted, feedback will be gained which will
lead to the need to adjust the plan(s).
CONSIDERATIONS FOR LARGER PROJECTS
In a large and/or complex OUM project, there may be several product evolutions –
one for each major release of the product to be developed, implemented or
upgraded. Projects which are more than a year in duration, those with high risk
factors and/or projects where there is business value to be gained from delivery of
a sub-set of the overall functionality are all candidates for the evolutionary
approach. This approach allows risk to be spread over a number of evolutions and
permits business value to be delivered sooner.
In the case where the multiple evolutions will be used to accomplish the project’s
objectives, an overall plan should be established to map out the evolutions. Each
evolution should be planned so that the delivery some subset of the project benefits
are realized through the delivery of working software and/or implementation of
Commercial Off-The-Shelf Software (COTS). This is done by examining the
business drivers and schedule goals for the project, laying out the work and
assigning the milestones in the roadmap to one or more evolutions. An example
evolution roadmap for a planning application is shown in Figure 5 below.
Planning a Project Using the Oracle Unified Method (OUM)
Page 12
13. Revenue &
Cost
Accounting
Integration
with Legacy
Accounting
Basic
Project
Planning
Analytics &
Reporting
Workflow
Evolution 1
Evolution 2
Integration
with Service
Providers
Evolution 3
Evolution 4
Figure 5: Example Evolution Roadmap
Once the overall plan for the evolutions is established, the planning details are
pushed to the lower level implementation and iteration plans for each evolution. As
the project progresses through the first evolution and subsequent evolutions more
information is brought to light which will require the plans at each layer to be
adjusted.
CONCLUSION
OUM recommends a layered approach to project planning rather than a single,
highly detailed plan. Planning and managing at each layer (implementation and
iteration) frees the project manager and project team from the need to create and
“feed” detailed plans that have a tendency to quickly become out of date and
unwieldy. The layered planning is scalable and empowers the team to focus on the
key goals, measurements, milestones and controls that enables effective project
management.
“All endeavor calls for the ability to tramp
the last mile, shape the last plan, endure
the last hours toil. The fight to the finish
spirit is the one... characteristic we must
possess if we are to face the future as
finishers.”
-
Henry David Thoreau
.
Planning a Project Using the Oracle Unified Method (OUM)
Page 13
14. REFERENCES
This white paper was made possible through the collaboration with numerous
OUM contributors as well as the conglomeration of information from several
outstanding books and websites:
•
Bittner, Kurt. 2007. Managing Iterative Software Development Projects. Boston,
MA: Pearson Education, Inc.
•
Boehm, B. and R. Turner. 2004. Balancing Agility and Discipline: A Guide for
the Perplexed. Boston, MA: Addison-Wesley
•
Cockburn, A. 2002. Agile Software Development. Boston, MA: AddisonWesley.
•
Larman, Craig. 2004. Agile and Iterative Development: A Manager’s Guide.
Boston, MA: Pearson Education, Inc.
•
Cohn, Mike, 1962 -. Agile estimating and Planning, Upper Saddle River, NJ:
Pearson Education, Inc.
•
A Guide to the Project Management Body of Knowledge (PMBOK®
Guide) – Fourth Edition, Newton Square PA: Project Management
Institute, Inc.
•
http://www.agilemanifesto.org.
•
http://alistair.cockburn.us
•
http://www.controlchaos.com/
•
http://martinfowler.com/articles/itsNotJustStandingUp.html
•
http://Agilesoftwaredevelopment.com/scrum
Planning a Project Using the Oracle Unified Method (OUM)
Page 14