So I have started an experiment: I ask various teams to define requirements for the same project, based on user stories/epics. We will compare the solutions and give everybody feedback and a possibility for discussion. I started by inviting a Danish consultancy company, specializing in agile. They immediately responded and soon sent their requirements. Would you give it a try too? Here is the assignment: Hotline Support (docx). It is a real-life project, small but a bit complex. The topic is rather easy to understand. Feel free to pass the assignment on.
|
Office IT University of Copenhagen Rued Langgaards Vej 7 DK-2300 Copenhagen S Phone, direct: +45 7218 5153 Phone, main: +45 7218 5000 Room: 4D24
|
Home Internet |
About SorenCV and interests Publication list Til danske siderProject failures and damagesLarge IT projects may be damaged in many ways, for instance large cost or schedule overruns, unsatisfied users, or disappointing business results. Sometimes the damages are so severe that the project is closed (complete failure). I have investigated several large projects and identified detailed causes of damage. I also provide suggestions on how to prevent the damages. See moreData visualization and electronic health recordsUvis - a tool for development of interactive graphical user screens: Uvis allows IT-interested users to develop complex data visualization screens. "Programming" the screens is done by formulas much like spreadsheet formulas. We implemented the tool and used it to develop an electronic health record system with advanced data visualization. As part of the project we also anonymized a large health record database. See moreWant help to write problem-oriented requirements? Simply send a message to: slauesen@itu.dk Problem-oriented requirements - SL-07Traditional requirements describe what the system shall do. Problem-oriented requirements (SL-07 requirements) describe what the users want to achieve and which problems to remedy. The requirements leave it to the supplier to show how his solution supports the users and handles the problems.The customer can assess how well the solution supports the users and use this in the supplier selection. The approach has many other advantages: Five times shorter, five times faster to write, five times faster to reply to, business goals met. Disadvantage: It takes three days to learn writing SL-07 requirements. See more Contract for SL-07 requirementsI have made an experiment: Put as much contract as possible into the requirements. Result: Contract now 8 pages rather than 50, requirements 4 pages longer, 23 damage causes prevented. See more (in Danish)UX and systematic design of user interfacesThere is still a big gap between usability specialists and software developers. The book User interface design - a software engineering perspective bridges the gap. It uses the Virtual Windows method where the data presentation screens are designed first, the dialog next. We also present two complex user interfaces designed this way. See moreMicrosoft-Access Tutorial (July 2011, 154 pages)This free book covers Access databases with advanced user interfaces and Visual Basic. Download (pdf) See more |
Soren CV Uvis health record Guide to SL-07 User interface design |
