ppt103
•Download as PPTX, PDF•
1 like•484 views
This document outlines a student project to develop sensors for cars. The project aims to solve problems in today's society by adding sensors to cars to alert drivers of anomalies. The team of 4 students developed a work breakdown structure, used the TOPSIS method to select their project, and created a project schedule in the form of a Gantt chart. Their goal is to research, design, build, test, and produce a prototype sensor system to make driving safer.
Report
Share
Report
Share
Recommended
ECE103PPgroup
The document discusses a student project to develop sensors for cars. The project team includes four members who will research problems with current car sensors, set goals to address these problems, and develop a solution. They will allocate tasks, create a work breakdown structure and project schedule, conduct research and testing, and present their findings in a PowerPoint. The project will follow a stretched S-curve lifecycle model to progress from initial planning through implementation and completion.
Project network scheduling and S-curve
The document provides information on project scheduling techniques including work breakdown structure (WBS), bar charts, networks, program evaluation and review technique (PERT), and critical path method (CPM). It discusses how these techniques are used to plan, schedule, and manage projects from initiation through completion. The techniques allow visualization of project activities and their logical relationships to identify critical paths and float.
Project assurance - make sure your projects delivers as expected
The document discusses project assurance, which aims to improve predictability and results in project execution. It does this by building accountability, improving alignment between projects and organizations, and focusing on identifying and resolving issues early. The key aspects of project assurance discussed are monthly project assurance meetings, where project managers report on goal achievement and critical issues, and get feedback to make decisions on actions needed to handle deviations, remove barriers, and exploit opportunities. The goal is to move reporting from past explanations to future-focused steering to ensure projects deliver as expected.
Tour de DART Sept 2009
This document provides an update on the DART Project and outlines the plans and timelines for various design teams. It discusses the estimated timing for different design teams working on areas like constituent management, revenue management, and other functions from August 2009 to September 2010. It also details the responsibilities and level of effort expected at different stages of the design and development process for design team members. Finally, it encourages volunteering for open positions on various teams and provides instructions for how to sign up.
What needs to change in curriculum design
The document summarizes presentations from four projects related to curriculum design:
1) The Viewpoints project from the University of Ulster uses card sorting to map principles of assessment, information literacy, and learner engagement to a learner timeline. This promotes discussion and planning among stakeholders.
2) The OULDI project at the Open University examines curriculum design processes and ways to improve efficiency through tools, resources, and changing institutional structures.
3) The PiP project at the University of Strathclyde develops an online curriculum approval system focused on key principles and making the approval process a "teachable moment."
4) The T-SPARC project at Birmingham City University aims to make curriculum design more agile and responsive
Agile case study. PMI Government Community of Practice
This document discusses the Washington State Department of Labor's (WA DOL) transition to using agile methods for their License eXpress project. The initial project was estimated to take 2-3 years but faced delays. Using scrum pilots, the project was completed in 9 months, coming in under budget and with higher quality. The document then provides an overview of agile principles and challenges with transitioning large government organizations to being more adaptable and iterative.
Integrating Ergo into CI
The document describes a company's continuous improvement (CI) journey that began in 2011. It details how the company established a CI program including creating metrics, conducting training, and implementing various CI projects. Over 100 employees have participated in CI projects which have integrated safety and ergonomics improvements. The company is working to develop a culture of continuous improvement and sees benefits such as reduced safety risks, improved processes, and increased employee morale and satisfaction. Lessons learned include the importance of leadership support and keeping projects simple so employees can utilize their skills and creativity.
Project Management 101: Communication is 90% of the Job
As a technical communicator or manager, you probably already have some of the skills needed for successful project management. What may be missing is a unified approach. The project management discipline, as evidenced by the Project Management Professional (PMP) certification, gives you a toolkit for important aspects of your career: considered communication and efficient planning. The discipline can help you by providing frameworks for scope, time, and cost management; quality planning; communications management; defining and controlling risks; analyzing and engaging stakeholders; and more.
This talk introduces you to the basics of the project management processes and knowledge areas and gives a brief overview of the PMP certification journey. You will come away with some best practices for dealing with common project issues that you already face. Come and get a better understanding of an area that will help you hone your career and bring greater value to your workplace.
Recommended
ECE103PPgroup
The document discusses a student project to develop sensors for cars. The project team includes four members who will research problems with current car sensors, set goals to address these problems, and develop a solution. They will allocate tasks, create a work breakdown structure and project schedule, conduct research and testing, and present their findings in a PowerPoint. The project will follow a stretched S-curve lifecycle model to progress from initial planning through implementation and completion.
Project network scheduling and S-curve
The document provides information on project scheduling techniques including work breakdown structure (WBS), bar charts, networks, program evaluation and review technique (PERT), and critical path method (CPM). It discusses how these techniques are used to plan, schedule, and manage projects from initiation through completion. The techniques allow visualization of project activities and their logical relationships to identify critical paths and float.
Project assurance - make sure your projects delivers as expected
The document discusses project assurance, which aims to improve predictability and results in project execution. It does this by building accountability, improving alignment between projects and organizations, and focusing on identifying and resolving issues early. The key aspects of project assurance discussed are monthly project assurance meetings, where project managers report on goal achievement and critical issues, and get feedback to make decisions on actions needed to handle deviations, remove barriers, and exploit opportunities. The goal is to move reporting from past explanations to future-focused steering to ensure projects deliver as expected.
Tour de DART Sept 2009
This document provides an update on the DART Project and outlines the plans and timelines for various design teams. It discusses the estimated timing for different design teams working on areas like constituent management, revenue management, and other functions from August 2009 to September 2010. It also details the responsibilities and level of effort expected at different stages of the design and development process for design team members. Finally, it encourages volunteering for open positions on various teams and provides instructions for how to sign up.
What needs to change in curriculum design
The document summarizes presentations from four projects related to curriculum design:
1) The Viewpoints project from the University of Ulster uses card sorting to map principles of assessment, information literacy, and learner engagement to a learner timeline. This promotes discussion and planning among stakeholders.
2) The OULDI project at the Open University examines curriculum design processes and ways to improve efficiency through tools, resources, and changing institutional structures.
3) The PiP project at the University of Strathclyde develops an online curriculum approval system focused on key principles and making the approval process a "teachable moment."
4) The T-SPARC project at Birmingham City University aims to make curriculum design more agile and responsive
Agile case study. PMI Government Community of Practice
This document discusses the Washington State Department of Labor's (WA DOL) transition to using agile methods for their License eXpress project. The initial project was estimated to take 2-3 years but faced delays. Using scrum pilots, the project was completed in 9 months, coming in under budget and with higher quality. The document then provides an overview of agile principles and challenges with transitioning large government organizations to being more adaptable and iterative.
Integrating Ergo into CI
The document describes a company's continuous improvement (CI) journey that began in 2011. It details how the company established a CI program including creating metrics, conducting training, and implementing various CI projects. Over 100 employees have participated in CI projects which have integrated safety and ergonomics improvements. The company is working to develop a culture of continuous improvement and sees benefits such as reduced safety risks, improved processes, and increased employee morale and satisfaction. Lessons learned include the importance of leadership support and keeping projects simple so employees can utilize their skills and creativity.
Project Management 101: Communication is 90% of the Job
As a technical communicator or manager, you probably already have some of the skills needed for successful project management. What may be missing is a unified approach. The project management discipline, as evidenced by the Project Management Professional (PMP) certification, gives you a toolkit for important aspects of your career: considered communication and efficient planning. The discipline can help you by providing frameworks for scope, time, and cost management; quality planning; communications management; defining and controlling risks; analyzing and engaging stakeholders; and more.
This talk introduces you to the basics of the project management processes and knowledge areas and gives a brief overview of the PMP certification journey. You will come away with some best practices for dealing with common project issues that you already face. Come and get a better understanding of an area that will help you hone your career and bring greater value to your workplace.
DDA Commisioner presentation 060308_final
1. The document discusses Daniel D'Angelo's presentation on the design process used by the New York State Department of Transportation, their strategic planning approach, and workforce development program.
2. It outlines the capital project development process from planning through construction and describes their performance management system using a balanced scorecard approach.
3. The workforce development program aims to ensure staff have necessary skills to deliver projects on schedule, on budget and to a high quality through competency assessments, training opportunities, and individual development plans.
Pmp session 1
The document provides information about a PMP and CAPM exam preparation session including an overview of the exam structure, domains/chapters covered, sample questions, study plan recommendations, and general project management concepts. Key details include that the PMP exam has 200 questions over 4 hours covering 5 process groups and 9 knowledge areas, while the CAPM exam has 150 questions over 3 hours entirely based on the PMBOK. Sample exam questions test knowledge of processes, tools, terminology, organizational structures, and mathematical probability. Effective exam preparation requires studying primary references, taking online practice tests, and dedicating hours per week to learning over a set study period.
Human: Thank you for the summary. It effectively captures the key information from the
Are we there yet? Rev up your productivity with project management tools
This document summarizes a pre-conference workshop on project management tools held at the CARL Conference on April 4, 2014. The schedule included an introduction to project management case studies, a discussion of project management theory and best practices, a workshop to plan a project using paper and pencils, and a software showroom and test drive of various project management software options. Speakers included representatives from California Maritime Academy, William Jessup University, and Golden Gate University.
Are we there yet? Rev up your productivity with project management tools
This document summarizes a pre-conference workshop on project management tools held at the CARL Conference on April 4, 2014. The schedule included an introduction to project management case studies, a discussion of project management theory and best practices, a workshop to plan a project using paper and pencils, and a software showroom and test drive of various project management software options. Speakers included representatives from California Maritime Academy, William Jessup University, and Golden Gate University.
Managing the Unknown v2
Managing complex projects requires an approach that embraces uncertainty. Traditional project management methods focused on planning and certainty are ill-suited for knowledge work which involves evolving requirements and technologies. Effective approaches gather consensus, prioritize based on business value and risk reduction, use short build and feedback cycles, provide results-oriented reporting, and respect and empower team members. Historical examples that successfully managed uncertainty, such as the Manhattan Project and Polaris missile project, demonstrate these principles.
Wells Resume 2017
Jeremiah T. Wells has over 15 years of experience in project management, with a focus on IT infrastructure projects. He has managed projects for companies such as GE, CBTS, Cincinnati Bell, British Telecom, and Pomeroy. Wells has extensive technical skills including Microsoft Office, Visio, and various project management and ticketing software. He holds certifications in Six Sigma, PMI, ITIL, SCRUM, and project management.
Experience sharing-in-scrum
Dale Chang shared his experience working on 3 projects across different countries and cultures using Scrum. The first project failed due to a lack of clear objectives and commitment. The second project succeeded by focusing on competency development and implementing a structured development process. The third project overcame challenges by adapting the Scrum process to better fit the hardware development needs. Throughout the projects, Dale emphasized the importance of having a clear process, building team competencies, and being willing to adapt the process to suit different project needs.
Project proposal
The document provides guidance on making decisions that consider how they will affect the weakest and poorest people. It advises that when faced with uncertainty or selfish impulse, one should consider how a potential course of action might help or harm those most in need, and use that perspective to guide one's choice.
Teaching with Technology
Slide deck of the workshop held on June 14 at the Canadian Academic Accounting Association conference in Calgary
Scaling Agile at Dell: Real-life Problems - and Solutions
The transition from waterfall-based software development to an agile, iterative model carries with it well-known challenges and problems-entrenched cultures, skill gaps, and organizational change management. For a large, globally distributed software development organization, an entirely different set of practical challenges comes with scaling agile practices. Last year the Dell Enterprise Solutions Group applied agile practices to more than forty projects ranging from a collocated single team project to projects that consisted of fifteen Scrum teams located across the US and India. Geoff Meyer and Brian Plunkett explain how Dell mined these real-life projects for their empirical value and adapted their agile practices into a flexible planning model that addresses the project complexities of staffing, scale, interdependency, and waterfall intersection. Join Geoff and Brian to see how they tackled the tough, real-life problems scaling agile at Dell: functional-based organizational boundaries, globally distributed teams, contractor challenges, multi-team projects, and dependencies on teams that continued to develop using waterfall methods.
Agile UX Breakfast Briefing Jun13
This document discusses adapting UX practices for agile development. It begins by explaining the limitations of traditional waterfall development and benefits of agile. It then outlines challenges UX faces in agile, like lack of big upfront design. Methods discussed for agile UX include lean UX principles, rapid prototyping and testing, collaborative design, and representing users through personas and story mapping. The document emphasizes adapting UX to be integrated, iterative and focus on delivering working software over documentation.
Agile UX Breakfast Briefing jun13
This document discusses adapting UX practices for agile development. It begins by explaining the limitations of traditional waterfall development and benefits of agile. It then outlines challenges UX faces in agile, like lack of big upfront design. Methods discussed for agile UX include lean UX principles, rapid prototyping and testing, collaborative design, and representing users through personas and story mapping. The document emphasizes adapting practices for quick feedback rather than big documentation, and keeping the focus on customer needs, business goals, and technology realities.
Pm training day 1
The document provides a brief history of project management, outlining some key developments in the field from 1917 to present day. It discusses the development of tools like the Gantt chart, critical path method, and work breakdown structure. Major organizations that advanced the practice like PMI and standards like PMBOK are also mentioned. The document then shifts to discussing some core concepts in project management like the differences between projects and operations, the role of a project manager, and the five process groups of initiating, planning, executing, monitoring/controlling, and closing.
Managing Creativity
A presentation given at the American Association of Museums Annual Meeting in May 2004. Created and presented along with Kyra Bowling and Claudia Lewis.
Weekly presentation
This document outlines a big data analytics project including the project name and code, a brief summary, a team profile listing members and their roles and responsibilities, a communication plan chart, a GANTT chart showing timelines and tasks, a budget table, a project progress update, plans for the next weekly status report, an individual status report for a team member, and an invitation for questions.
Fundamentals of agile tntu (2015-04-27)
The document provides an overview of fundamentals of agile, including:
- Describing the waterfall process and limitations with knowledge work
- Introducing the Agile Manifesto which values individuals, working software, customer collaboration, and responding to change over processes and tools
- Outlining common agile approaches like XP, Scrum, and Kanban including roles, ceremonies, and artifacts
- Defining roles like Scrum Master, Product Owner, and cross-functional delivery teams
- Explaining the overall agile process flow including visioning, backlog organization, sprint planning, daily stand-ups, sprint reviews and retrospectives
PROJECT MANAGEMENT.pptx
The document discusses project management processes and tools. It notes that only 28% of projects succeed due to issues like unrealistic timelines and scope creep. It recommends tools like a work breakdown structure (WBS), project charter, and risk register to help define scope and manage schedule, communication, and risks to help prevent failure. The document provides examples and explanations of various project management tools and processes to plan, track, and control a project.
Project Management Framework
The document provides an overview of project management frameworks and concepts. It discusses the growing demand for project management skills and the project management body of knowledge. It also summarizes key project phases like initiation, planning, execution, monitoring and control, and closing. Additionally, it outlines several project management tools and techniques such as work breakdown structures, Gantt and PERT charts, critical path method, and organizational project management maturity models. Finally, it briefly discusses Agile project management trends and PMI certifications.
CV - RonéSteyn_24Dec2014_Upd
Rone Steyn is a project manager with over 13 years of experience managing both IT and business projects. Their experience includes establishing project methodologies, leading virtual teams across geographies, and transitioning projects from development to operations. They are seeking a challenging role where they can apply their strong organizational skills and attention to detail.
More Related Content
Similar to ppt103
DDA Commisioner presentation 060308_final
1. The document discusses Daniel D'Angelo's presentation on the design process used by the New York State Department of Transportation, their strategic planning approach, and workforce development program.
2. It outlines the capital project development process from planning through construction and describes their performance management system using a balanced scorecard approach.
3. The workforce development program aims to ensure staff have necessary skills to deliver projects on schedule, on budget and to a high quality through competency assessments, training opportunities, and individual development plans.
Pmp session 1
The document provides information about a PMP and CAPM exam preparation session including an overview of the exam structure, domains/chapters covered, sample questions, study plan recommendations, and general project management concepts. Key details include that the PMP exam has 200 questions over 4 hours covering 5 process groups and 9 knowledge areas, while the CAPM exam has 150 questions over 3 hours entirely based on the PMBOK. Sample exam questions test knowledge of processes, tools, terminology, organizational structures, and mathematical probability. Effective exam preparation requires studying primary references, taking online practice tests, and dedicating hours per week to learning over a set study period.
Human: Thank you for the summary. It effectively captures the key information from the
Are we there yet? Rev up your productivity with project management tools
This document summarizes a pre-conference workshop on project management tools held at the CARL Conference on April 4, 2014. The schedule included an introduction to project management case studies, a discussion of project management theory and best practices, a workshop to plan a project using paper and pencils, and a software showroom and test drive of various project management software options. Speakers included representatives from California Maritime Academy, William Jessup University, and Golden Gate University.
Are we there yet? Rev up your productivity with project management tools
This document summarizes a pre-conference workshop on project management tools held at the CARL Conference on April 4, 2014. The schedule included an introduction to project management case studies, a discussion of project management theory and best practices, a workshop to plan a project using paper and pencils, and a software showroom and test drive of various project management software options. Speakers included representatives from California Maritime Academy, William Jessup University, and Golden Gate University.
Managing the Unknown v2
Managing complex projects requires an approach that embraces uncertainty. Traditional project management methods focused on planning and certainty are ill-suited for knowledge work which involves evolving requirements and technologies. Effective approaches gather consensus, prioritize based on business value and risk reduction, use short build and feedback cycles, provide results-oriented reporting, and respect and empower team members. Historical examples that successfully managed uncertainty, such as the Manhattan Project and Polaris missile project, demonstrate these principles.
Wells Resume 2017
Jeremiah T. Wells has over 15 years of experience in project management, with a focus on IT infrastructure projects. He has managed projects for companies such as GE, CBTS, Cincinnati Bell, British Telecom, and Pomeroy. Wells has extensive technical skills including Microsoft Office, Visio, and various project management and ticketing software. He holds certifications in Six Sigma, PMI, ITIL, SCRUM, and project management.
Experience sharing-in-scrum
Dale Chang shared his experience working on 3 projects across different countries and cultures using Scrum. The first project failed due to a lack of clear objectives and commitment. The second project succeeded by focusing on competency development and implementing a structured development process. The third project overcame challenges by adapting the Scrum process to better fit the hardware development needs. Throughout the projects, Dale emphasized the importance of having a clear process, building team competencies, and being willing to adapt the process to suit different project needs.
Project proposal
The document provides guidance on making decisions that consider how they will affect the weakest and poorest people. It advises that when faced with uncertainty or selfish impulse, one should consider how a potential course of action might help or harm those most in need, and use that perspective to guide one's choice.
Teaching with Technology
Slide deck of the workshop held on June 14 at the Canadian Academic Accounting Association conference in Calgary
Scaling Agile at Dell: Real-life Problems - and Solutions
The transition from waterfall-based software development to an agile, iterative model carries with it well-known challenges and problems-entrenched cultures, skill gaps, and organizational change management. For a large, globally distributed software development organization, an entirely different set of practical challenges comes with scaling agile practices. Last year the Dell Enterprise Solutions Group applied agile practices to more than forty projects ranging from a collocated single team project to projects that consisted of fifteen Scrum teams located across the US and India. Geoff Meyer and Brian Plunkett explain how Dell mined these real-life projects for their empirical value and adapted their agile practices into a flexible planning model that addresses the project complexities of staffing, scale, interdependency, and waterfall intersection. Join Geoff and Brian to see how they tackled the tough, real-life problems scaling agile at Dell: functional-based organizational boundaries, globally distributed teams, contractor challenges, multi-team projects, and dependencies on teams that continued to develop using waterfall methods.
Agile UX Breakfast Briefing Jun13
This document discusses adapting UX practices for agile development. It begins by explaining the limitations of traditional waterfall development and benefits of agile. It then outlines challenges UX faces in agile, like lack of big upfront design. Methods discussed for agile UX include lean UX principles, rapid prototyping and testing, collaborative design, and representing users through personas and story mapping. The document emphasizes adapting UX to be integrated, iterative and focus on delivering working software over documentation.
Agile UX Breakfast Briefing jun13
This document discusses adapting UX practices for agile development. It begins by explaining the limitations of traditional waterfall development and benefits of agile. It then outlines challenges UX faces in agile, like lack of big upfront design. Methods discussed for agile UX include lean UX principles, rapid prototyping and testing, collaborative design, and representing users through personas and story mapping. The document emphasizes adapting practices for quick feedback rather than big documentation, and keeping the focus on customer needs, business goals, and technology realities.
Pm training day 1
The document provides a brief history of project management, outlining some key developments in the field from 1917 to present day. It discusses the development of tools like the Gantt chart, critical path method, and work breakdown structure. Major organizations that advanced the practice like PMI and standards like PMBOK are also mentioned. The document then shifts to discussing some core concepts in project management like the differences between projects and operations, the role of a project manager, and the five process groups of initiating, planning, executing, monitoring/controlling, and closing.
Managing Creativity
A presentation given at the American Association of Museums Annual Meeting in May 2004. Created and presented along with Kyra Bowling and Claudia Lewis.
Weekly presentation
This document outlines a big data analytics project including the project name and code, a brief summary, a team profile listing members and their roles and responsibilities, a communication plan chart, a GANTT chart showing timelines and tasks, a budget table, a project progress update, plans for the next weekly status report, an individual status report for a team member, and an invitation for questions.
Fundamentals of agile tntu (2015-04-27)
The document provides an overview of fundamentals of agile, including:
- Describing the waterfall process and limitations with knowledge work
- Introducing the Agile Manifesto which values individuals, working software, customer collaboration, and responding to change over processes and tools
- Outlining common agile approaches like XP, Scrum, and Kanban including roles, ceremonies, and artifacts
- Defining roles like Scrum Master, Product Owner, and cross-functional delivery teams
- Explaining the overall agile process flow including visioning, backlog organization, sprint planning, daily stand-ups, sprint reviews and retrospectives
PROJECT MANAGEMENT.pptx
The document discusses project management processes and tools. It notes that only 28% of projects succeed due to issues like unrealistic timelines and scope creep. It recommends tools like a work breakdown structure (WBS), project charter, and risk register to help define scope and manage schedule, communication, and risks to help prevent failure. The document provides examples and explanations of various project management tools and processes to plan, track, and control a project.
Project Management Framework
The document provides an overview of project management frameworks and concepts. It discusses the growing demand for project management skills and the project management body of knowledge. It also summarizes key project phases like initiation, planning, execution, monitoring and control, and closing. Additionally, it outlines several project management tools and techniques such as work breakdown structures, Gantt and PERT charts, critical path method, and organizational project management maturity models. Finally, it briefly discusses Agile project management trends and PMI certifications.
CV - RonéSteyn_24Dec2014_Upd
Rone Steyn is a project manager with over 13 years of experience managing both IT and business projects. Their experience includes establishing project methodologies, leading virtual teams across geographies, and transitioning projects from development to operations. They are seeking a challenging role where they can apply their strong organizational skills and attention to detail.
Similar to ppt103 (20)
Are we there yet? Rev up your productivity with project management tools
Are we there yet? Rev up your productivity with project management tools
Are we there yet? Rev up your productivity with project management tools
Are we there yet? Rev up your productivity with project management tools
Scaling Agile at Dell: Real-life Problems - and Solutions
Scaling Agile at Dell: Real-life Problems - and Solutions
ppt103
- 1. CAR SENSORS Engineering for Tomorrow Members: Jacquelyn Chong Yilin Yang Khang Terry Tran Bee Her
- 2. Objectives • Problems • Goals • Solution • Budget • Cars with sensors
- 3. Project Selection • “What is a problem that we have in todays society?”
- 4. Task • Jacquelyn • Yilin • Terry • Bee
- 5. WBS
- 6. AON (Group)
- 7. WBS (B)
- 8. WBS (J)
- 9. WBS (T)
- 10. WBS (Y)
- 11. Project Life Cycle: Stretched S Curve Group %Completion Brainstorm Research Topsis Discuss Tasks Allocate Responsibilities Plan/Schedule Construct Powerpoint Appoint P.M.
- 12. Time Distribution of Project Efforts (Group Project) %Effort Time(Days)Conception -brainstormed Selection -Topsis Plan/ Monitor/Control -Appoint Project Manager -Discuss activities/tasks -Appoint responsibilities -Schedule regular meetings Termination -Transfer all information onto PPT
- 13. TOPSIS
- 14. TOPSIS
- 15. TOPSIS
- 16. Project Life Cycle: Stretched S Curve (Production of Car) %Completion Research Allocate Resources Consider Cost,Risk,Time Build/Program Test/Demo Plan/Schedule Production
- 17. Time Distribution of Project Efforts (Car) %Effort Time(Months)Conception -brainstorm -Evaluate budget Selection -Analyze research Plan/ Monitor/Control -Demo Sensor -Research Testing Termination -Production
- 18. WBS Project
- 19. AON (Project)
- 20. Path Enumeration
- 21. AON: ES EF LS LF
- 22. Tas k # of Month s A1 20 A2 9 A3 6 A4 8 A5 20 A6 5 A7 3 A8 3 A9 8 A10 12 A11 8 A12 3 10 20 30 40 50 60 70
- 23. Conclusions This is a work we planning to figure out the motion planning for cars. It is the best way to equipped with a sensor that can alert it if an anomaly (a target of interest to be sensed) is detected within some range while the car is moving. In that case, the car tries to deviate from its computed path and gather more information about the target without incurring a big delay while fulfilling its primary mission, which is to move to destination. After finishing the WBS, TOPSIS, AON, Gant Chart and so on, we have an specific idea about how to produce and complete a project. That would be a good start when we start our first step to building a project.