My manager give me the task to implement new ISO procedures of analysis and design (later it will be of the entire software development cycle) because in the team we don't have any kind of methodology to develop the requested software which tend to be a "developer do what they want thing".
My manager wants to implement SCRUM (I've reading about it, just to have a general idea) but because in SCRUM the steps are iterative the team decide which process will they use (decisions of how gather the requirements, how design x UI, how you should program), I'm feeling that it conflicts with having a technical procedure of how the things should be done.
Is there a general requirement discovering in SCRUM? Like interviews, surveys with the client and then those stack of requirements are shared with the team in the multiple sprint meetings for the backlog or it's a continue discovering with the team and the stakeholders (users stories in the sprint meetings)
I have to create a design procedure, which will describe how to approach UI design (mockups, prototype, etc), in SCRUM is not up to the team how they do it?
An analyst will follow this procedures and after a view of what the project is going to be share it with the team to begin the implementation, though removing the responsibility of recreating the entire development process for each application without an specific methodology.
I know the questions are not specific to the main question, however the answers of them will help me to find an answer.
I'm not going for any certifications, all the procedures in the company are made with the standard ISO 27001, but I'm more in a draft process with trial and error.
What the management want is an established procedures of how the development cycle will be, which I found a little difficult to merge with the AGILE/SCRUM methodology (maybe I need to research more about it) because things as flow as the work is evolved and put persons over process.