flightmanmicah

Thank you Thank you all who are working so diligently to keep this modification of Kerbal Space Program running. I understand the difficulty and the struggle when juggling work, school, and projects such as this one. I truly am wishing you the best of luck in resolving this issue. To everyone else on this forum, patience is key. CommanderSpock is sorting out the issue and reorganizing the team. Please be patient with him as he gets everything back in order. If you wish to help, wait until the current team members are reorganized into a better working group. Respectfully, flightmanmicah http://forum.kerbalspaceprogram.com/entries/3739-Organization-Important-During-Development

Let. Me. Help.

Let me help. I have the ability.

Okay, I really want you guys to succeed on this! Let me know if I can help.

Sampa, Mike-nz, You guys figure out the organization yet and what the goals are? Having those will help. Because the next step would be courses of action, which is really where the fun is.

This is why you need to be given tasks, lol.

Then create a document that outlines what the final product should be, the stepping stones to getting there, and how to reach each stepping stone. Basically, the three levels of goals.

What is the full release, what does it all include? Will it be final with no expansions or will there be expansions? When will it be done? If you can answer these questions, then they just need to be told to the project team. Then, make the middle stuff. Again, I am willing to help but I don't want to be in charge.

That is part of what we like to call, "Research Stage" in project management. It is where you find out what the users want. It is honestly my least favorite part put that's just me. So, a great idea would be to simply ask that question, "What do you want to see as a part of the Space Shuttle Program?" Make it a google drive form. Post a link like the poll and see what you get after three days. Compile the list of what the users want, figure out what is possible, select those possible outcomes as the final product, create a mission statement for the project team, create long-term, mid-term, and short-term goals, then develop courses of actions to achieve those goals. BINGO! Organization at its finest! After the publication of the final product, refine it as necessary and fix bugs as necessary. This is why major products have updates, like operating systems. After all of that is said and done, if the users start asking for more, start thinking of making an expansion pack later on.

That's generally what happens when you don't have assistance or an objective to accomplish. Having short, mid, and long term goals gives people purpose and drive. Through the courses of action it allows members of the team to see their progress and continue to work with diligence.

It all comes down to what the final product should look like. For where there is no vision, the people perish.

I would be willing to assist in the direction of the project, not manage it though. Here's the big deal, goals have to be set. These are the kind of questions we have to answer: What do we want as a final product? - Shuttle, ground facilities, launch vehicle, Extras, payloads, all of it. What do we want six months from now? - Shuttle and ground facilities What do we want six weeks from now? - Shuttle and launch vehicle That's just a quick example.

That's good an all but being more specific also helps. Its like writing a paper, if you do an outline it makes things easier when writing. The more work put into the outline, the easier the writing will be and usually the better the final product will be.

That comes from the course of actions developed after the goal setting session.

I'm technically a nobody right now with this but may I make a suggestion? Great! The problem that occurred last time was a lack of direction/goal of the project. In project management, something I am quite familiar with, the project team must first come up with short-term, mid-term, and long-term goals before any work occurs. Without this goal setting portion, the ship is basically without a rudder and is taken hither and thither by the four winds. I suggest that you stop development, sit down with the entire team or at least the top three of the project management and set some goals. When the goals are set, creative courses of actions can be, well, created (who, what, when, where, why) for each goal and a timeline for each as well. This may take a bit of time but imagine just being able to sit down and have everything already laid out on when it needs to be done and what needs to be done! All this being said, I'm not in the management team and I am not certain as to what has actually already been discussed off the cuff and what is going on behind the scenes but it seems like there is a lack of direction among the project team. Hope this helps. Cheers.