Content in the Videos category
You are part of a modern development team delivering new features like clockwork. But are you sure you’re delivering the right features? Are you relying on up-front product research practices that don’t fit with your development process?
Product design and development remains difficult, even when applying Lean or Agile principles. Why is developing a great product so hard? How come it takes so many iterations? Why don’t users know what they want? Why don’t I know what they want?
Creating requirements for your web or mobile application can be tedious and managing ideas even more. The larger the project, the more difficult it becomes. Add in the flexibility that Agile brings to projects, and things could quickly get out of hand.
Learn how leading organizations are investing more in requirements as part of their product development strategy to give everyone involved a common vision of what is being built and who the customer is. Without that common vision even the best teams risk writing the wrong test, focusing on the wrong design elements, or moving the wrong item to the top of the backlog.
How do agile requirements work? Where does documentation fit in? For many of us, the transition from the security of upfront analysis and detailed specification documents to ‘doing Agile’ and embracing the process of discovery is a terrifying prospect. Agile theories don’t readily address the concern ‘how will we know where we’re going if we don’t start with a Business Requirement Specification?’
How do you know what to build of your customer wants a “secure solution with a good amount of flexibility and user friendliness”? You don’t! Force the customer to be more specific!
This video explores split testing as a way to not only increase revenue and conversion through simple, surface-level changes, but also to dig deeper in order to help guide a product’s roadmap by discovering which features customers really want and how much they’re willing to pay.
By now, we are all comfortable with the orthodoxy: the product owner discerns the needs of the customer and feeds them to developers in the form a prioritized backlog. Developers pull work from that backlog, always confident that they’re working on the highest-priority feature at the moment, and never having to worry about how those priorities are allocated. This system is simple, efficient, and has helped many teams function better than they used to. It’s also time for the system to die.
Wondering how to step up your business analyst career, and take on responsibilities of your appointed tasks with professionalism, enthusiasm and efficiency? Learn what makes a good business analyst, a GREAT business analyst, with pointers and guidance from an industry professional.
Cherifa Mansoura, Agile Solution Architect at IBM, discusses requirements gathering, change management, user stories, and more as it relates to Agile software development practices.