Skip to main content

Timeline for Agile Artifacts

Current License: CC BY-SA 3.0

8 events
when toggle format what by license comment
Feb 5, 2018 at 17:17 comment added Ashok Ramachandran @bobo2000 The above question was about creating a project plan and baselining it for an agile project. If you have a question on doing the software architecture up-front, please post a separate question.
Feb 5, 2018 at 16:27 comment added bobo2000 Doesn't work, never will work and will cause people to build blindly creating more problems in the long run. For example, it's a lot quicker and cheaper to document software architecture, have it peer reviewed, than to build it blindly and make it up as you go along. Very hard to change once it's been created. Don't get me wrong, I love agile, but it's about being pragmatic about what to use from the framework
Feb 5, 2018 at 15:20 comment added Ashok Ramachandran @bobo2000 Agile favors working software over comprehensive documentation. You do need a Product Owner fully engaged with the team to do the prioritization and help with the acceptance criteria. Also, make sure to demo working features to the stakeholders at the end of each sprint and get their feedback.
Feb 5, 2018 at 14:17 comment added bobo2000 I get that, the thing is if you spent the first 3 weeks requirement gathering, you can significantly break epics down and do a high level plan. I have worked in 'agile' environments where there is no documentation at all, and it is complete chaos from nobody knowing what is going on. Documentation is so important for getting people up to speed and general handover.
Feb 5, 2018 at 14:12 history edited Ashok Ramachandran CC BY-SA 3.0
minor edit
Feb 3, 2018 at 14:55 comment added Ashok Ramachandran @bobo2000 See my answer to your question in the other thread.
Feb 3, 2018 at 10:15 comment added bobo2000 Why can't you factor in requirement gathering in your project plan?
Feb 1, 2018 at 16:29 history answered Ashok Ramachandran CC BY-SA 3.0