Everything that is needed to develop working software in terms of project management is described in Frederick Brooks "The Mythical Man-Month".
Design software. Do incremental development. Half of the code should be automatic tests (doesn't have to be unit tests, that are often waste of time, functional test is typically more useful).
Unlike many, if not most, "Agile" proponents Brooks actually took part in creation of a really robust and badass piece of software, IBM's OS/360.
In addition to corporate agiles like Scrum of SAF (SAF is a true abomination, all the most stupid ideas put into one bucket, but expensive SAF certificate expires after a year and has to be repurchased, so they make a lot of money) there are also anecdotal agiles, like Basecamp "Shape Up" that probably can work if you have a lot of time, mature fashionable product that sells itself anyway and you don't have to answer to annoying customers.
All of this is mostly buzzword filled bullshit. Waste of time.
Design software. Do incremental development. Half of the code should be automatic tests (doesn't have to be unit tests, that are often waste of time, functional test is typically more useful).
Unlike many, if not most, "Agile" proponents Brooks actually took part in creation of a really robust and badass piece of software, IBM's OS/360.
In addition to corporate agiles like Scrum of SAF (SAF is a true abomination, all the most stupid ideas put into one bucket, but expensive SAF certificate expires after a year and has to be repurchased, so they make a lot of money) there are also anecdotal agiles, like Basecamp "Shape Up" that probably can work if you have a lot of time, mature fashionable product that sells itself anyway and you don't have to answer to annoying customers.
All of this is mostly buzzword filled bullshit. Waste of time.