3 ms·
> In $current_company, I was surprised that none of the basics were there. All agree to do these things, but with the slightest bit of pressure those principles
by mamcx 6y ago
> In $current_company, I was surprised that none of the basics were there. All agree to do these things, but with the slightest bit of pressure those principles are gone
This is the normal. I think I have never be in a project with the "proper" stuff from the start.
I have applied what I can, not even asking (because the answer will be "no?"), so the fact that:
> All agree to do these things..
You are set! that is the key!. Now, how do this successfully?
Pick only 1 thing to solve (like I say, almost daily, to Stakeholder of the projects "One problem(or miracle!) at time").
The first is "use source control" OR "use a task manager/bug tracker".
For a project with more non-developers, the second will be MORE useful.
The key is use the most simple thing you can get. I use pivotal, ignore it for all the SCRUM stuff, and only use it to list the task to be done, task doing and done, and train everyone with this ONLY rule "Put what is more important from top to bottom".
That is literary, the only process that I use with others. With non-developers, I not even try to expect them to label correctly bugs vs features, and most of time I rewrite the task myself (for clarity).
But man, people, specially non devs, love to see the progress of the project! This relieve so much presure is insane.
So the key:
* Pick only 1 thing to improve at time
* Use the more simple tool/process possible
For example, use git, only 2 branches (master, dev)
* Accept some imperfect inputs from people that are not skilled in the trade
"My users will never reporte correctly a bug, so I rewrite the reports after talk to them"
And for others "the devs never put a good message in commit", then
* Pick only 1 thing to improve at time
if are in the phase of "at least using git!" not sweat it. Maybe gently remming them
And probably:
* Have a mega list of good things to do in the task manager, and cross milestones with the team. Celebrate when done!