I would like to get some expert opinion on the following product environment in terms of story writing and story slicing. Suppose if we have an enterprise product and many clients would be onboarding to the product in different timelines of deadlines with customized extra features than the basic product. As many clients are getting onboarded with more unique customized features and the overlap is in place, the Product owners are getting challenges in writing the story which enriches the base product that fits our system and slicing the stories into smaller units that fit into the 2-week sprint for the clients. What would be your suggestion or approaches on these sort of situations to address the story writing and slicing challenges?
A good leader keeps everything in order. In this fast-paced era where agile methodologies have become a more often used framework, a good Scrum Master is what is needed. But what makes a good Scrum Master?
Sometimes a challenge can be turned into an opportunity. When our team learned that the business needed to pull their popular Product Owner to focus on another team, a sense of panic set in. There would be a job search that could and did take months. Who would help the team on their path to creating value in the interim? How would we operate? Over time, what seems to be a negative turn of events was turned upside down.
Calling all software development project team members having Daily Stand-Up Meetings (DSMs).
My name is James Gray and I am mature student studying an MSc in Project Management at Solent University. I am undertaking research into how productivity can be affected by the start time of the Daily Stand-Up Meeting (DSM) within software development projects. I would be most grateful if you have the time to assist. All responses will be anonymous and the survey should take between 5 – 10 minutes.
The rapid rate of technological change is forcing enterprises to reinvent themselves and provide more flexible approaches, so agile transformations are key. However, knowing that agile is important is one thing, but the ability to properly implement the main principles, tools, and techniques of agile is another. Let’s explore time-tested agile principles that will help your organization build innovative products that customers love.
Ryan Ripley, professional Scrum trainer at Scrum.org, chats with TechWell community manager Owen Gotimer about what Scrum is, some of the most common Scrum antipatterns, and the importance of connecting your Scrum team with your customer. Continue the conversation with Ryan and Owen (@owen) on the TechWell Hub (http://hub.techwell.com/)!
Refinement is time spent during the current sprint discussing and elaborating product backlog items so that they are ready for future sprints. Unfortunately, many teams do not unlock the full potential of refinement. Backlog items should be sliced, and a solution should be proposed, reviewed, and discussed. If your team is having trouble getting started, here are 18 questions you can use to trigger refinement discussions.
Tech support is notorious for having a bad reputation about their service, both on the receiving side and the serving side. Fortunately, the situation is improving, particularly in innovative organizations that are adopting an agile approach to tech support. Agile is helping customer service teams prioritize tasks, collaborate, and continuously improve. What can you do to be agile in your organization’s tech support?
Agile isn't something you can adopt through tooling; you have to adhere to agile principles every step of the way. The top articles from 2019 show that people were looking to enhance and advance their agile practices, with popular topics including how to empower your team throughout agile adoption, using metrics to improve, refining Scrum practices, and scaling agile. Check out this roundup for ways to boost your agile operations.