Posts

Showing posts with the label requirements

Management Tactics for the real world complex projects

A lot of management practices are used to optimize to current state of the projects and get the situation under control, but it does not always work as intended. Unfortunately, many people think that just applying the required process does the trick, however, in many cases it does not. I've published the presentation Management Tactics regarding that, and you can find the corresponding notes with the detailed explanations below.

Seven Ws (composing brief software requirements)

Quis, quid, quando, ubi, cur, quem ad modum, quibus adminiculis. (Who, what, when, where, why, in what way, by what means) Hermagoras of Temnos Quotation above is created by Hermagoras for defining seven "circumstances" as a way of the formulating or analyzing rhetorical questions. But it is useful for many other areas, like for composing brief software requirements. Sometimes it's essential for us to analyze the perspective project as fast as possible, without creating tremendous SRS, but merely ask few questions and begin to work. Especially, it relates to Agile Development, and can be easily used as a reference point for starting a project. Let us interpret these questions to ones of the sample meanings: Who will use that project? What kind of software does the project represent? When should the project be delivered to the end users? Where is the project intended to be used? Why would the project be successful? In what way is the project supposed to w...