Jump to content
  • Advertisement
Sign in to follow this  
OSmith

Production Management Portfolio Advice

This topic is 549 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi there,

 

I recently finished work on a PSVR project over the last four months as Producer of a small team, and was wondering which aspects of production would be of most interest to discuss in a portfolio.

 

For the most part I was curious if it would be more interesting to talk about the challenges that cropped up during development (For instance the difficulties of scheduling when having to work with such specific and occasionally volatile technology) , or to focus on the broad strokes of how the project was managed and what I learnt from it.

 

Any feedback on that would be appreciated,

 

Thanks

Share this post


Link to post
Share on other sites
Advertisement

Just link the project.

 

It's site and overall quality is  part of your portfolio.

 

If someone is interested in that aspect of your work, they will ask you questions on the spot about it. And if your unable to answer on the spot, then you don't know yourself or the project enough.

 

As a producer, you are intimately connected with the health of the project, if your not, your not doing it right. 

 

Hyperlink it in your resume, and break down your responsibilities.

 

Make sure you say it was 4 months, and  why it was developed.

 

There is a huge problem in the hiring for games, that has been going on for a while.

 

People put the title on the resume, and neglect to clarify it was for a game jam or the duration, it makes it so frustrating for recruiters to filter out who actually has professional  and long term experience. 

 

You will not get a call back from AAA unless your hobby experience crosses over into  a few years, so don't spend too much time agonizing how to sell it. (unless you mean 4 months full time paid for play station Virtual Reality )

Edited by GeneralJist

Share this post


Link to post
Share on other sites

For the most part I was curious if it would be more interesting to talk about the challenges that cropped up during development (For instance the difficulties of scheduling when having to work with such specific and occasionally volatile technology) , or to focus on the broad strokes of how the project was managed and what I learnt from it.

 

It sounds like you know what is relevant. I don't think you should talk about "what you learnt from it" - that sounds like something a teacher would ask you to write. Instead, word it as "which skills you used on it" - the fact that you learnt them as you went along is immaterial.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!