Project Management Stack Exchange is a question and answer site for project managers. It only takes a minute to sign up.
Sign up to join this community
I have been a developer for awhile. Recently, I got promoted within my team. Now I am responsible for application design and documentation, and am thinking of following the Scrum methodology.
We are starting a new project. As I am new to Design and Documentation, I am curious to know how many types of documents are required and in what order these documents must be written. Are there any references to required documents that I can look at?
Scrum is not a development methodology; it's a project management methodology. The Scrum process holds no specific answers for you from a requirements standpoint.
However, Scrum holds that the questions you are asking are part of the self-organizing that your team must do to be successful, including defining sprint goals and your team's "definition of done." As a result, you will need to look to your team (specifically including your Product Owner) to determine what specific design and documentation artifacts you need to produce to meet your sprint goals, and the prioritized order assigned to each of those artifacts.
(I started this as a comment, maybe it should be just a comment)
"How detailed it should be"...
the scrum answer would be:
as simple as it can be so that all parties know what to expect from each other....
I know this does not help you much right now in the beginning.
Agile is based on continous improuvement, and that's not only about code, but also about how code is created, documented. CI is also about the comunication in the team and between stakeholders.
It is about finding the way with the least management overhead for your team to deliver results that satisfy your customer. Because this varies between teams, customers and countries, scrum does not give any details about how documents are created, only that at least 3 documents be created.
