Take the 2-minute tour ×
Project Management Stack Exchange is a question and answer site for project managers. It's 100% free, no registration required.

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?

share|improve this question
1  
I assume you will have read the "normal" design documents from previous projects. Is there something specific that does not meet your needs. Most of the time the manager just wants you to use whatever method or process ha sbeen in use in the company. Or did he tell you to go ahead and think of some new ways.... –  Huibert Gill Jul 28 '12 at 18:20
    
@HuibertGill I was asked to work on "High-level project Document" which all stake holders are interested to see. This should contain lot of UML in it. I don't have any reference documents. So wondering, if I can get any help here? –  HaBo Jul 29 '12 at 2:06
    
@HaBo UML document design is not a project management task. While you may have to perform the task within a project, that has nothing to do with the framework or the scope of the PM role. In fact, "where can I find..." questions are pretty much off-topic on every Stack Exchange site, so you'll have to do some independent research on that one. Good luck! –  CodeGnome Jul 29 '12 at 21:00
add comment

2 Answers 2

Scrum Does Not Prescribe Development Practices

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.

Scrum Provides a Framework for Your Questions

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.

See Also

share|improve this answer
    
you are right. I have to start with preparing "High-level project Document" I wasn't sure what should be my check list in it. what all aspects of my project, should be covered in this document and how detailed is this supposed to be? –  HaBo Jul 29 '12 at 2:08
add comment

(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.

share|improve this answer
    
Some practitioners may argue over that definition, but the three documents you reference are generally agreed to be: product backlog, sprint backlog, and project/sprint burndown charts. scrum-agile-methodology.com/scrum-methodology.html –  CodeGnome Jul 29 '12 at 17:15
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.