At the OOP 2015 conference Colin Hood talked about bridging the gap between requirements engineering process definition and successful iterative roll-out. He presented how the introduction of improvements to requirements engineering can be done better when done step by step, and how relative safety is needed to enable people to take the steps.
In agile software development feedback plays an important role. Many are aware how feedback supports dealing with changing requirements and adjusting the way of working in teams with retrospectives. But there is more that feedback can do in agile. “An effective feedback cycle in Scrum is more than having sprints and doing retrospectives” says Kris Philippaerts.
At the recent Project Management Institute Global Congress the Business Analysis Practice Guide was announced, to complement the Professional in Business Analysis certification which was launched in November. InfoQ spoke to Dave Bieg, Business Analysis and Requirements Program Manager about the certification and the practice guide.
At GOTO Amsterdam 2013, Russ Miles did a lightning talk about building the right thing in 5 questions: the 4 questions from impact mapping “Why? Who? How? and What?” and one additional question “What assumptions underpin everything?”. InfoQ did an interview with him about building the right thing using simplicity.
An exploration on how project management with Scrum and the project management process areas of the Capability Maturity Model Integration for Development are related.
Enterprise software startups use a minimum viable product (MVP) to learn about customers with limited effort and money. How can organizations deploy lean startup principles to develop a viable product for their stakeholders?