FTC:Engineering Portfolio - Revision history

ManiacMechanics: (corrected team number)

2024-04-14T03:26:54Z

(corrected team number)

← Older revision		Revision as of 03:26, 14 April 2024
Line 38:		Line 38:

	==Examples==		==Examples==
	* [http://www.spontaneousconstruction.com/wp-content/uploads/2021/08/EN-Portfolio.pdf ~~FTC14779~~ Spontaneous Construction - 2022 Engineering Portfolio]		* [http://www.spontaneousconstruction.com/wp-content/uploads/2021/08/EN-Portfolio.pdf FTC 14779 Spontaneous Construction - 2022 Engineering Portfolio]
	* [https://maniacmechanics.weebly.com/uploads/1/3/2/0/132089891/2021-2022_18082_portfolio_of_engineering-compressed.pdf ~~FTC18082~~ Maniac Mechanics - 2022 Engineering Portfolio]		* [https://maniacmechanics.weebly.com/uploads/1/3/2/0/132089891/2021-2022_18082_portfolio_of_engineering-compressed.pdf FTC 18082 Maniac Mechanics - 2022 Engineering Portfolio]
	*[https://maniacmechanics.weebly.com/uploads/1/3/2/0/132089891/20230114_portfolio.pdf ~~FTC18082~~ Maniac Mechanics - 2023 Engineering Portfolio]		*[https://maniacmechanics.weebly.com/uploads/1/3/2/0/132089891/20230114_portfolio.pdf FTC 18082 Maniac Mechanics - 2023 Engineering Portfolio]
	*[https://www.theponytailposse.com/about/engineering-notebook-archive/ ~~FTC8088~~ Ponytail Posse - 2014-2018 archive]		*[https://www.theponytailposse.com/about/engineering-notebook-archive/ FTC 8808 Ponytail Posse - 2014-2018 archive]

	==Additional Resources==		==Additional Resources==

ManiacMechanics: Added another example

2024-04-14T03:25:27Z

Added another example

← Older revision		Revision as of 03:25, 14 April 2024
Line 41:		Line 41:
	* [https://maniacmechanics.weebly.com/uploads/1/3/2/0/132089891/2021-2022_18082_portfolio_of_engineering-compressed.pdf FTC18082 Maniac Mechanics - 2022 Engineering Portfolio]		* [https://maniacmechanics.weebly.com/uploads/1/3/2/0/132089891/2021-2022_18082_portfolio_of_engineering-compressed.pdf FTC18082 Maniac Mechanics - 2022 Engineering Portfolio]
	*[https://maniacmechanics.weebly.com/uploads/1/3/2/0/132089891/20230114_portfolio.pdf FTC18082 Maniac Mechanics - 2023 Engineering Portfolio]		*[https://maniacmechanics.weebly.com/uploads/1/3/2/0/132089891/20230114_portfolio.pdf FTC18082 Maniac Mechanics - 2023 Engineering Portfolio]
			*[https://www.theponytailposse.com/about/engineering-notebook-archive/ FTC8088 Ponytail Posse - 2014-2018 archive]

	==Additional Resources==		==Additional Resources==

ManiacMechanics: Added current-year's EP

2023-03-11T22:27:05Z

Added current-year's EP

← Older revision		Revision as of 22:27, 11 March 2023
Line 38:		Line 38:

	==Examples==		==Examples==
	* [http://www.spontaneousconstruction.com/wp-content/uploads/2021/08/EN-Portfolio.pdf FTC14779 Spontaneous Construction - ~~Minnesota State Tournament -~~ Engineering Portfolio]		* [http://www.spontaneousconstruction.com/wp-content/uploads/2021/08/EN-Portfolio.pdf FTC14779 Spontaneous Construction - 2022 Engineering Portfolio]
	* [https://maniacmechanics.weebly.com/uploads/1/3/2/0/132089891/2021-2022_18082_portfolio_of_engineering-compressed.pdf FTC18082 Maniac Mechanics - ~~Minnesota State Tournament~~ - Engineering Portfolio]		* [https://maniacmechanics.weebly.com/uploads/1/3/2/0/132089891/2021-2022_18082_portfolio_of_engineering-compressed.pdf FTC18082 Maniac Mechanics - 2022 Engineering Portfolio]
			*[https://maniacmechanics.weebly.com/uploads/1/3/2/0/132089891/20230114_portfolio.pdf FTC18082 Maniac Mechanics - 2023 Engineering Portfolio]

	==Additional Resources==		==Additional Resources==

ManiacMechanics: /* Examples */

2022-11-18T03:08:27Z

Examples

← Older revision		Revision as of 03:08, 18 November 2022
Line 39:		Line 39:
	==Examples==		==Examples==
	* [http://www.spontaneousconstruction.com/wp-content/uploads/2021/08/EN-Portfolio.pdf FTC14779 Spontaneous Construction - Minnesota State Tournament - Engineering Portfolio]		* [http://www.spontaneousconstruction.com/wp-content/uploads/2021/08/EN-Portfolio.pdf FTC14779 Spontaneous Construction - Minnesota State Tournament - Engineering Portfolio]
			* [https://maniacmechanics.weebly.com/uploads/1/3/2/0/132089891/2021-2022_18082_portfolio_of_engineering-compressed.pdf FTC18082 Maniac Mechanics - Minnesota State Tournament - Engineering Portfolio]

	==Additional Resources==		==Additional Resources==

Ian: added links to other pages

2022-06-22T22:02:52Z

added links to other pages

← Older revision		Revision as of 22:02, 22 June 2022
Line 5:		Line 5:
	\|robots=index, follow		\|robots=index, follow
	}}		}}
	The Engineering Portfolio is a summary of a [[FIRST:About\|''FIRST'']] Tech Challenge (FTC) team and what they have accomplished during their season. The portfolio is limited to 15 pages. It is the only required documentation and can be used to intrigue the judges so they want to read more detail in an [[FTC:Engineering Notebook\|Engineering Notebook (EN)]], if the team has one. The portfolio should only be the tip of the iceberg compared to the team's documentation, everything should be in the EN. The portfolio is a documentation tool for a team to show their journey throughout the season. It should be an example of a team's decision-making process and a record of their progress. The portfolio is meant to display all the aspects of a team’s work including, hardware, software, outreach, experiments, and any other category that is important to the team.		The Engineering Portfolio is a summary of a [[FIRST:About\|''FIRST'']] Tech Challenge (FTC) team and what they have accomplished during their season. The portfolio is limited to 15 pages. It is the only required documentation and can be used to intrigue the judges so they want to read more detail in an [[FTC:Engineering Notebook\|Engineering Notebook (EN)]], if the team has one. The portfolio should only be the tip of the iceberg compared to the team's documentation, everything should be in the EN. The portfolio is a documentation tool for a team to show their journey throughout the season. It should be an example of a team's decision-making process and a record of their progress. The portfolio is meant to display all the aspects of a team’s work including, [[FTC:Hardware\|hardware]], [[FTC:Software\|software]], [[FTC:Outreach\|outreach]], experiments, and any other category that is important to the team.

	The important thing to remember is that all the information should be clear to the judges. They don’t have background knowledge about a team that a member does. The judges need context when reading a portfolio, so organize the content carefully and use clear wording. Visuals like pictures of the robot or design diagrams are very helpful, so add them whenever possible (a picture is worth a thousand words). It is difficult to find the balance between detailed and reader-friendly content. Especially when documenting decisions, each option should be explained and the final choice should be clear.		The important thing to remember is that all the information should be clear to the judges. They don’t have background knowledge about a team that a member does. The judges need context when reading a portfolio, so organize the content carefully and use clear wording. Visuals like pictures of the robot or design diagrams are very helpful, so add them whenever possible (a picture is worth a thousand words). It is difficult to find the balance between detailed and reader-friendly content. Especially when documenting decisions, each option should be explained and the final choice should be clear.

Ian at 19:11, 16 April 2022

2022-04-16T19:11:32Z

← Older revision		Revision as of 19:11, 16 April 2022
Line 5:		Line 5:
	\|robots=index, follow		\|robots=index, follow
	}}		}}
	The Engineering Portfolio is a summary of a [[FIRST:~~about~~\|''FIRST'']] Tech Challenge (FTC) team and what they have accomplished during their season. The portfolio is limited to 15 pages. It is the only required documentation and can be used to intrigue the judges so they want to read more detail in an [[FTC:Engineering Notebook\|Engineering Notebook (EN)]], if the team has one. The portfolio should only be the tip of the iceberg compared to the team's documentation, everything should be in the EN. The portfolio is a documentation tool for a team to show their journey throughout the season. It should be an example of a team's decision-making process and a record of their progress. The portfolio is meant to display all the aspects of a team’s work including, hardware, software, outreach, experiments, and any other category that is important to the team.		The Engineering Portfolio is a summary of a [[FIRST:About\|''FIRST'']] Tech Challenge (FTC) team and what they have accomplished during their season. The portfolio is limited to 15 pages. It is the only required documentation and can be used to intrigue the judges so they want to read more detail in an [[FTC:Engineering Notebook\|Engineering Notebook (EN)]], if the team has one. The portfolio should only be the tip of the iceberg compared to the team's documentation, everything should be in the EN. The portfolio is a documentation tool for a team to show their journey throughout the season. It should be an example of a team's decision-making process and a record of their progress. The portfolio is meant to display all the aspects of a team’s work including, hardware, software, outreach, experiments, and any other category that is important to the team.

	The important thing to remember is that all the information should be clear to the judges. They don’t have background knowledge about a team that a member does. The judges need context when reading a portfolio, so organize the content carefully and use clear wording. Visuals like pictures of the robot or design diagrams are very helpful, so add them whenever possible (a picture is worth a thousand words). It is difficult to find the balance between detailed and reader-friendly content. Especially when documenting decisions, each option should be explained and the final choice should be clear.		The important thing to remember is that all the information should be clear to the judges. They don’t have background knowledge about a team that a member does. The judges need context when reading a portfolio, so organize the content carefully and use clear wording. Visuals like pictures of the robot or design diagrams are very helpful, so add them whenever possible (a picture is worth a thousand words). It is difficult to find the balance between detailed and reader-friendly content. Especially when documenting decisions, each option should be explained and the final choice should be clear.

Ian: added link to first about

2022-04-16T19:10:56Z

added link to first about

← Older revision		Revision as of 19:10, 16 April 2022
Line 5:		Line 5:
	\|robots=index, follow		\|robots=index, follow
	}}		}}
	The Engineering Portfolio is a summary of a ''FIRST'' Tech Challenge team and what they have accomplished during their season. The portfolio is limited to 15 pages. It is the only required documentation and can be used to intrigue the judges so they want to read more detail in an [[FTC:Engineering Notebook\|Engineering Notebook (EN)]], if the team has one. The portfolio should only be the tip of the iceberg compared to the team's documentation, everything should be in the EN. The portfolio is a documentation tool for a team to show their journey throughout the season. It should be an example of a team's decision-making process and a record of their progress. The portfolio is meant to display all the aspects of a team’s work including, hardware, software, outreach, experiments, and any other category that is important to the team.		The Engineering Portfolio is a summary of a [[FIRST:about\|''FIRST'']] Tech Challenge (FTC) team and what they have accomplished during their season. The portfolio is limited to 15 pages. It is the only required documentation and can be used to intrigue the judges so they want to read more detail in an [[FTC:Engineering Notebook\|Engineering Notebook (EN)]], if the team has one. The portfolio should only be the tip of the iceberg compared to the team's documentation, everything should be in the EN. The portfolio is a documentation tool for a team to show their journey throughout the season. It should be an example of a team's decision-making process and a record of their progress. The portfolio is meant to display all the aspects of a team’s work including, hardware, software, outreach, experiments, and any other category that is important to the team.

	The important thing to remember is that all the information should be clear to the judges. They don’t have background knowledge about a team that a member does. The judges need context when reading a portfolio, so organize the content carefully and use clear wording. Visuals like pictures of the robot or design diagrams are very helpful, so add them whenever possible (a picture is worth a thousand words). It is difficult to find the balance between detailed and reader-friendly content. Especially when documenting decisions, each option should be explained and the final choice should be clear.		The important thing to remember is that all the information should be clear to the judges. They don’t have background knowledge about a team that a member does. The judges need context when reading a portfolio, so organize the content carefully and use clear wording. Visuals like pictures of the robot or design diagrams are very helpful, so add them whenever possible (a picture is worth a thousand words). It is difficult to find the balance between detailed and reader-friendly content. Especially when documenting decisions, each option should be explained and the final choice should be clear.

Leigha at 04:08, 14 April 2022

2022-04-14T04:08:26Z

← Older revision		Revision as of 04:08, 14 April 2022
Line 5:		Line 5:
	\|robots=index, follow		\|robots=index, follow
	}}		}}
	The Engineering Portfolio is a summary ~~about~~ a team and what they have accomplished during their season. The portfolio is limited to 15 pages. It is the only required documentation and can be used to intrigue the judges ~~and make them~~ want to read more detail in an [[FTC:Engineering Notebook\|Engineering Notebook (EN)]], if the team has one. The portfolio is a documentation tool for a team to show their journey throughout the season. It should be an example of a team's decision-making process and a record of their progress. The portfolio is meant to display all the aspects of a team’s work including, hardware, software, outreach, experiments, and any other category that is important to the team.		The Engineering Portfolio is a summary of a ''FIRST'' Tech Challenge team and what they have accomplished during their season. The portfolio is limited to 15 pages. It is the only required documentation and can be used to intrigue the judges so they want to read more detail in an [[FTC:Engineering Notebook\|Engineering Notebook (EN)]], if the team has one. The portfolio should only be the tip of the iceberg compared to the team's documentation, everything should be in the EN. The portfolio is a documentation tool for a team to show their journey throughout the season. It should be an example of a team's decision-making process and a record of their progress. The portfolio is meant to display all the aspects of a team’s work including, hardware, software, outreach, experiments, and any other category that is important to the team.

	The important thing to remember is that all the information should be clear to the judges. They don’t have background knowledge about a team that a member does. The judges need context when reading a portfolio, so organize the content carefully and use clear wording. Visuals like pictures of the robot or design diagrams are very helpful, so add them whenever possible (a picture is worth a thousand words). It is difficult to find the balance between detailed and reader-friendly content. Especially when documenting decisions, each option should be explained and the final choice should be clear.		The important thing to remember is that all the information should be clear to the judges. They don’t have background knowledge about a team that a member does. The judges need context when reading a portfolio, so organize the content carefully and use clear wording. Visuals like pictures of the robot or design diagrams are very helpful, so add them whenever possible (a picture is worth a thousand words). It is difficult to find the balance between detailed and reader-friendly content. Especially when documenting decisions, each option should be explained and the final choice should be clear.

	==Content==		==Content==
	The ~~portfolio~~ has some elements that are necessary for the competition:		The Engineering Portfolio has some elements that are necessary for the competition:
	* '''Team''' - a section including team member and coach bios		* '''Team''' - a section including team member and coach bios
	* '''Hardware''' - a section containing engineering content that outlines how the engineering process is used in the building of the robot		* '''Hardware''' - a section containing engineering content that outlines how the engineering process is used in the building of the robot

Leigha at 04:18, 4 March 2022

2022-03-04T04:18:03Z

← Older revision		Revision as of 04:18, 4 March 2022
Line 1:		Line 1:
			{{#seo:
			\|title=FTC Engineering Portfolio - Project Robotica
			\|keywords=FTC, FIRST Tech Challenge, Engineering Portfolio, EP, Portfolio, Judging Materials, Documentation
			\|description=The FTC Engineering Portfolio is a 15-page document containing a summary of teams’ journey through the season and it is submitted for judging.
			\|robots=index, follow
			}}
	The Engineering Portfolio is a summary about a team and what they have accomplished during their season. The portfolio is limited to 15 pages. It is the only required documentation and can be used to intrigue the judges and make them want to read more detail in an [[FTC:Engineering Notebook\|Engineering Notebook (EN)]], if the team has one. The portfolio is a documentation tool for a team to show their journey throughout the season. It should be an example of a team's decision-making process and a record of their progress. The portfolio is meant to display all the aspects of a team’s work including, hardware, software, outreach, experiments, and any other category that is important to the team.		The Engineering Portfolio is a summary about a team and what they have accomplished during their season. The portfolio is limited to 15 pages. It is the only required documentation and can be used to intrigue the judges and make them want to read more detail in an [[FTC:Engineering Notebook\|Engineering Notebook (EN)]], if the team has one. The portfolio is a documentation tool for a team to show their journey throughout the season. It should be an example of a team's decision-making process and a record of their progress. The portfolio is meant to display all the aspects of a team’s work including, hardware, software, outreach, experiments, and any other category that is important to the team.

Leigha at 02:24, 14 August 2021

2021-08-14T02:24:50Z

← Older revision		Revision as of 02:24, 14 August 2021
Line 32:		Line 32:

	==Examples==		==Examples==
	* ~~FTC14779 Spontaneous Construction - Minnesota State Tournament -~~ [http://www.spontaneousconstruction.com/wp-content/uploads/2021/08/EN-Portfolio.pdf/ Engineering Portfolio]		* [http://www.spontaneousconstruction.com/wp-content/uploads/2021/08/EN-Portfolio.pdf FTC14779 Spontaneous Construction - Minnesota State Tournament - Engineering Portfolio]

	==Additional Resources==		==Additional Resources==