written by gunther gerlach-2009
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.
Gunther Gerlach
written by gunther gerlach-2009
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.
Gunther Gerlach
written by gunther gerlach-2009
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.
Gunther Gerlach
