So not sure what the are into but before dis'ing SCRUM, it is one of many Agile methodologies used in software development. And a very effective one. Here is a link to a very easy to read book that explains it well:
Agile Project Management with Scrum (Developer Best Practices) https://www.amazon.com/dp/073561993X/ref=cm_sw_r_apan_glt_fabc_SDX22V0Y6DQ4PEP9CA7A
Just dont want scrum to get a scrummy name :)
I would agree with you but understand that when Ken Schwaber, one of the founders of scrum, began teaching Scrum he had a class called Agile Project Management with Scrum. For the majority of people who have no idea what scrum this is probably the best way to introduce the idea, even though, yes, it's not really a Project Management framework, but a manage "complex products and services as a team" framework.
I’d say that, as long as your musician is charging you reasonably, option 2 seems like a good start. I’d say you should finalize what you want your game to be about (it’ll change in the beginning, almost definitely) and the mood of it. If you settle on cartoonish artwork, you want your composer to make a cartoony soundtrack. But there is no point in having them make that, and then changing to be a completely different atmosphere. In conclusion, I’d say it’s probably best to go to your composer when you have your idea down and have determined that it is fun. From there, work with them for the entire development process. If they are in on what is going on, and not just getting told what to make, they may pick up on an underlying idea that you can’t place your finger on so that the music will truly fit your vision. And as Wlad Marhulets says in his book, “A composer can become an equal part of the team who provides valuable feedback from an audio standpoint. Such feedback could be very useful and might influence your approach to game design, pacing, and storytelling.” And in the same book, a quote from composer Austin Wintory, “For ‘Journey’ I got to be on the front lines of the development team for all three years. I offered my thoughts and let their ideas have an imprint on my music. The results wouldn’t have been the same otherwise.”
Awesome!! I'd say going to school for it is a great start!
I'd make sure to get involved with any construction specific student orgs. Alot of them are affiliated with professional orgs like the AGC, ABC and NAHB. On top of that, any more experience or internships you can get will do you well!
Here's a $15 textbook from Amazon. It's a great read, not your typical dry learning. Construction Management JumpStart: The Best First Step Toward a Career in Construction Management https://www.amazon.com/dp/0470609990/ref=cm_sw_r_cp_apa_tU5MAb2GW7Z3F
Also try to kinda get an idea of what sector you'd want to lean towards. Some schools make you specialize in home building, commercial, or heavy civil.
Making Things Happen: Mastering Project Management by Scott Berkun is great.
I read an earlier edition when it had a better title "The Art of Project Management"
Not a podcast but I found these cd's very helpful for the same reason. It was a great way to maximize my study time: Conversations on the PMP Exam: How to Pass on Your First Try
This book covers the basic processes of construction from pre-design to O&M, as well as the different delivery methods (Traditional, CM At Risk, Design-Build, etc), as well as most of the terms you will need. It is required reading for the introduction class where I went to school. There is a kindle edition:
http://www.amazon.com/Construction-Management-JumpStart-Toward-Career/dp/0470609990
Right now it is rough around the edges. However, they have a road map for full DSC support. Jeffrey Snover, creator of Powershell and DSC has said chef aligns most with their goals.
So, I'd say it will be the best bet. But, you can get a lot done with a pull server and VM templates.
Checkout this book on Kindle http://www.amazon.com/Windows-PowerShell-Desired-Configuration-Revealed/dp/1484200179
First of all huge upvotes to ell0bo and BabylonDrifter. They touch on actual manager issues as opposed to programmer issues.
Your job as a manager depends on the size of the team/company, but it is never to code or even make design decisions - hopefully you have people under you which are much better at that. What a good manager should be doing is manage people!
As someone with a programmer background my idea of managing a project was skewed towards the technical aspects, a book which helped me understand a lot of the actual managing and people issues was this, I highly recommend it:
http://www.amazon.com/Making-Things-Happen-Mastering-Management/dp/0596517718