1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Which project management style, e.g. Waterfall, Agile, Lean is the bestest?

Discussion in 'General Technology Discussions' started by Yellow Fang, 23 Nov 2017.

  1. Yellow Fang

    Yellow Fang Über Geek

    Location:
    Reading
    Anyone got any opinions on development styles? My new employers want me to set one up. I am used to Waterfall, which might suit MoD projects, but I have never found it worked. I worked under various slightly ad hoc management styles . In one job, project engineers relayed requests for new features and fixes to the project manager who discusses it with the software manager, who distributes the work to the programmers. The software manager would keep track either by weekly meetings or going around the programmers every couple of days to check how they were doing. At my last job we used Agile SCRUM, which I did not like. I found it stressful. It's a good idea to have some way of divvying up work, and checking that the programmers aren't stuck, or engaged unproductively. I was thinking about looking into Kanban or Lean engineering.
     
  2. amusicsite

    amusicsite dn ʎɐʍ sᴉɥ┴ Staff Member

    Location:
    UK
    Is the problem with most systems. One of the first jobs I had as a back end programmer was to build a system so workers could estimate how long a job should take when assigned it and then log their hours every day. So the boss and staff could look at the estimates and see if they were accurate. I must say, this really taught me a good lesson on monitoring how long I spend on tasks. It also meant the boss, or project manager, could easily spot problems when things were flagged up as going well over the estimated time to complete.

    Documentation is also a great way of keeping track of project development. Make them submit a report every so often on the changes to the documentation from what they have been doing. It's also a great way to make sure the documentation is being done and kept up to date.

    I always think the best solution is to work out what you need to track and how the projects should flow first, then look at which system fits it best. Or make a bespoke system tailored for your needs, which you can also customise if you need. It's so easy to set up a management system with a web server and a few lines of code. I could get one up and running in days.

    It's always better to tailor your system to a workflow that people are comfortable with and know rather than try and teach people a whole new system that may be better. Code is easier to change than people, so a bespoke system you can easily change can be adapted to whatever you encounter.
     
    Yellow Fang likes this.
  3. Yellow Fang

    Yellow Fang Über Geek

    Location:
    Reading
    I have just been reading about different management styles. I have worked under SCRUM, which personally I did not enjoy. I read a book on Kanban. I think some variant of Kanban is the only system that would have worked at my last company. I have just been reading about XP (Extreme Programming). This includes pair programming. I cannot see that being very popular at some of the places I have worked. Some of the best programmers are rugged individualists, especially the contractors. They just would not accept it. There is typically quite a range of ability amongst programmers in a project, and some personalities are more dominant than others. I just can't see it working. I may be wrong, though.