Use Cases: are in fact such a clear description of a feature, and the fact that each Use Cases could stand alone. They made it really easy to move cards representing the Use Cases around the
As a difference between this methodology from the others is that Agile Development teams capture requirements at a high level only, just-in-time for each feature to be developed. Agile scrum methodology requirements are ideally visual and should be barely sufficient, i.e. the absolute minimum required to enable development and testing to proceed with reasonable efficiency. The rationale for this is to minimise the time spent on anything that doesn’t actually form part of the end product.
Use Cases: are in fact such a clear description of a feature, and the fact that each Use Cases could stand alone. They made it really easy to move cards representing the Use Cases around the whiteboard, as a way of managing progress. The downside of the Use Cases is that they are a little complicated. When you look closely, they’re not that complicated really. But they tend to need a Business Analyst to write them. And they tend to be a bit off-putting for end users or business people.
Define your Sprint duration:A Sprint is a key when agile scrum process is implemented in SDLC. The Sprint defines the amount of time where a team will release a feature or list of features from a giving sprint backlog. This is an important decision. Scrum suggests 30 days, but they could a week if you estimate that will improve your team efficiency. The optimum Sprint duration depends on many factors. I suggest going back to your team and analyzing the perfect duration to be able of releasing a piece of software. I suggest 14 days, plus a planning day for your team and Stake Holders to create the product backlog prioritize requirements form different teams and, analyze the product burn chart. This will leave 2 weeks of intensive work and also, two Sprints a month.
If we go back to the basics, I would define User Stories as a simple tool of communication to capture user requirements throughout a project based on the business requirements and stake holder’s needs. This is a perfect, easy and fast alternative to writing extensive requirements specifications to start developing. While the technical issues and integration problems are hard to find with a simple overview of the business or technical requirements, the user Histories give some time a better overview of the details by a simple and descriptive walk, step by step by every process.
There is an easy way to work with a team remotely and share documents from diverse sources like MS word, Excel, Power Point and many others, without failing in duplication of information or having different version of the same documents. This is an issue that it need to be fix and who better than Google with its online applications (SaaS: Software as a Service) running over their powerful grid and web services platform.
Watch this video and you will understand in few minutes all the benefits of working with virtual documents.
Usually projects start very easy, everyone is exited and ready to work on it but in reality, for most of the player on those discovery and pre-design meetings, such as developers and designer, there is no much to do yet and they are focused on their current projects being carried out in parallel so, technical issues and integration problems are hard to find with a simple overview of the business or technical requirements.
written by gunther gerlach-2009
written by gunther gerlach-2009
written by gunther gerlach-2009
written by gunther gerlach-2009
written by gunther gerlach-2009
