Manage

Software Requirements Management

• How to tame ever-changing requirements in software development

  When one sprint ends, another begins -- but not before you receive a heaping new pile of requirements. Here's how to deal with requirements changes efficiently, every time, any time. Continue Reading

• Apache exec talks prudent open source software project usage

  The open source community faces a number of technical and existential threats. A veteran talks open source's role, funding, security and compliance, as well as his favorite projects. Continue Reading

• What you need to know about the ALM methodology

  Gerie Owen provides an overview of ALM methodology, covering its requirements, development and maintenance phases and its core components. Continue Reading

• QA should be present for Agile story mapping

  What is a respectful way to insist that QA and other stakeholders be included in Agile story mapping for new projects? Continue Reading

• How do testers influence acceptance criteria?

  What's the tester's role in establishing user stories and acceptance criteria? Expert Amy Reichart discusses how much influence a tester should have. Continue Reading

• How do requirements relate to acceptance criteria?

  Requirements and acceptance criteria often seem to be essentially the same thing, but that's not quite true.Continue Reading

• Does Agile use business requirements documents?

  How does managing requirements differ in an Agile environment versus a mixed-methodology environment? How do Agile project managers document business requirements?Continue Reading

• Right focus on requirements prevents feature creep

  To prevent feature creep, product requirements should satisfy the actual business requirements. Creep can occur when product requirements are detailed but business requirements are too general.Continue Reading

• Software lifecycle: Rethinking requirements - and the tester's role

  When specifying requirements at the outset of software lifecycle, maybe "less is more"-- and testers should step up to fill in the gaps.Continue Reading

• Good software design and development starts with customers' needs

  Discovering customer needs isn't a simple query and response. It takes some work to get the information your design and development efforts rely on.Continue Reading

• Release manager on software rollout: Let business goals drive code changes

  An experienced release manager offers advice on software rollouts: Let business goals and tight controls drive code changes.Continue Reading

• Software defects increase cost of Agile projects

  Fixing software defects can increase the cost of Agile software development projects, according to a recent voke inc. survey.Continue Reading

• Continuous delivery in ALM: Opportunities and challenges

  Continuous delivery is the automation of the software build-test-deployment of software cycles; sometimes it allows for completing the cycle multiple times a day.Continue Reading

• Strategies for scaling Agile beyond simple code-and-deploy environments

  In this tip, consultant Michael Kelly shares some models and strategies that will help teams stay Agile as projects grow.Continue Reading

• Adopting Agile: Eight traction tips to make Agile development stick

  Agile transition isn't easy. The tendency may be to revert back to traditional methods once the going gets tough, though experts encourage organizations to stick with it. In this tip, we learn eight tips for Agile traction recommended by Howard ...Continue Reading