Labs Engineering Guide

Welcome!

Please read this first!!

This space is a collection of how-to documents related to the various tools, frameworks, tools and platforms that are using in Labs. These guides are closely related to the Labs Engineering Standards document.

Contributing

These are living documents that try to represent a fast moving and ever-changing tech landscape. As such, there will be errors and omissions as parts of these guides fall out-of-date.

If you find gaps or issues in these documents, please feel free to open an issue in the corresponding GitHub repo. You are also welcome to submit a pull request, which will be reviewed by Labs managers.

Glossary

Product

A business term for a set of applications, service or other resources that provide some value to an end-user or other system.

• A Product may exist for a very long time or sometimes not long at all

• A Product may be implemented in many different ways and the implementation may change completely at some point during its lifespan

• A Product is a logical construct (aka logical entity), meaning it's just a name that groups together a set of People, Projects and Resources

Product Role

A set of skills and responsibilities required to make a Product successful. Product Roles are filled by people who have the required skills (or will learn them quickly!) and will take on the responsibilities to make the Product successful.

• Typical Product Roles:

  • Product Manager, Product Stakeholder, Product Designer, etc.

• Product Roles can change over time, as the needs and the lifecycle of the Product evolves

• A Product Role is a logical construct; it's just a name given to a set of skills and responsibilities.

• When you are part of a Product, you are actually playing a Role on that Product. Your Product Role defines the items you a responsible or accountable for.

Project

A business term for a group people that are working to build, fix, extend or otherwise enhance a Product for some period of time.

• A Project is associated with one and only one Product.

• A Project has a pre-defined set of Roles required for the Project to be successful.

• People are assigned to one or more Roles on a Project, which helps guides their work.

• A Project has a specific starting point and a specific end point. The end point can either be when a specific amount of time has passed or specific set of tasks have been completed.

Project Role

A set of skills and responsibilities required to make a Project successful. Project Roles are filled by people who have the required skills (or will learn them quickly!) and will take on the responsibilities to make the Project successful.

• Typical Project Roles:

  • Project Manager, Lead Engineer, UX Designer, Web Developer, Data Scientist, Mobile Engineer, etc.

• Project Roles can change over time, as the needs and the lifecycle of the Project evolves

• A Project Role is a logical construct; it's just a name given to a set of skills and responsibilities.

• When you are part of a Project, you are actually playing a Role on that Project. Your Project Role defines the items you a responsible or accountable for.

AWS Product Account

An AWS account that hosts all of the various AWS resources required to run a particular student Product.

There is only one AWS account per Product that is shared by all Project teams.