I am assuming that you have reasonably well rounded experience as a programmer and are well versed in your organisations standards and methodologies. If not, then my advice is probably not going to be much use. I have re-trained Cobol and RPG programmers to develop OOP systems using the following. And I have taught SE at university so I have some experience, but never with complete absolute non-programming mindset folks.
"Ship a feature in a couple of months" ... WTF? ... is you management even sane???
Putting that brain snap aside ...
You need to establish what programming language, framework, tools, conventions you will be using. Then with that in mind, create a series of progressive exercises that introduce basic programming concepts (as are applicable to the features that you will be expected to ship over the next 12-18 months). Basically you would do a "teaching session" with handouts, examples and some live-coding on your part. Then you follow that with a "tutorial session" where your team gets to practice what they have just learnt. For a week or two that is all that you are likely to be able to achieve.
Once you get over that initial hurdle, you would need to design that first feature and assign segments to each member of the team. During that time you will be mentoring and assessing how well each member of the group is "coping".
Realistically, if you could complete the required feature on your own in one month, then the above exercise will probably take three months. But the next feature will take probably half that if your team come up to speed at about average rate.
For your sake, I suggest that you have your management on-side. I have seen too many managers who think that programming is nothing more than typing. Those PHBs are the bane of any software development project.
I am aware that this is becoming a long read. But I hope that your team is not expected to do analysis nor design. That has to be done by people with considerable domain and development expertise.
"Ship a feature in a couple of months" ... WTF? ... is you management even sane???
Putting that brain snap aside ...
You need to establish what programming language, framework, tools, conventions you will be using. Then with that in mind, create a series of progressive exercises that introduce basic programming concepts (as are applicable to the features that you will be expected to ship over the next 12-18 months). Basically you would do a "teaching session" with handouts, examples and some live-coding on your part. Then you follow that with a "tutorial session" where your team gets to practice what they have just learnt. For a week or two that is all that you are likely to be able to achieve.
Once you get over that initial hurdle, you would need to design that first feature and assign segments to each member of the team. During that time you will be mentoring and assessing how well each member of the group is "coping".
Realistically, if you could complete the required feature on your own in one month, then the above exercise will probably take three months. But the next feature will take probably half that if your team come up to speed at about average rate.
For your sake, I suggest that you have your management on-side. I have seen too many managers who think that programming is nothing more than typing. Those PHBs are the bane of any software development project.
I am aware that this is becoming a long read. But I hope that your team is not expected to do analysis nor design. That has to be done by people with considerable domain and development expertise.