SOP on Agile
Just as an untamed climber through beautiful adds no value to your garden, with it's rapid growth all over the place, so does untrackable project management. We are aware of many methods from legacy to agile, however, these are just tools and names which can not get you to your goal. The Key to managing projects is to make sure the tasks flow naturally from assignment to completion. This article highlights some Standard Operating Procedures (SOP) towards an Architecture centric project management. It could be used as a guideline to check if the natural flow of the project is maintained. I also use these SOPs sometimes as a way to mitigate risks by asking the right questions.
SOP1: Understand the System Principles First: gives you the why and where?
SOP2: Understand the Architects approach: gives you the business case and the whys?
SOP3: Meetings and workshops and MOM: to make sure the stakeholders are happy
**Also TBD in next blog : https://www.slideshare.net/mkconway/introduction-to-scenario-planning
** Start with Why : https://g.co/kgs/Q7XQBq
SOP4: Start with Agile (not methods) user stories and objectives: context is more important than the content, let the context define the method.
SOP5: Automation is not magic: Always Design before you code or autogenerate code.
SOP6: No to local drives, yes to the configuration management:
SOP7: Think before you commit:
SOP7: Don't rush for bug fixing: have you asked the right questions
SOP8: Lessons Learnt: You are not always right :
SOP9: Keep calm with crucial conversations :
SOP10: Yor is alive if you are learning and sharing: