How do you keep your retrospectives fresh and the team engaged? It is a challenge many agile teams face. As organisations adjust to running almost every meeting online, the issue of conference call fatigue is making this even more important. To run effective agile retrospectives in any climate you need an efficient delivery approach that will spur your team. Remote or face to face, it is essential to keep the retrospective short, focused and engaging - read on to find out how.
The last few months have been challenging for most Sales teams, and ours has been no exception. The uncertainty of the economic climate has led many businesses to hibernate. In the space of a couple of weeks, the market went quiet; projects were put on hold, budgets cut.
In my experience, when working with Interactive Grid, most of the times, we need to open a modal popup to interact with selected records (single or multi selection). For example, let say we have an Interactive Grid listing some records and you want a button which bulk updates all selected rows with the same value.
The quality of communication within a project team is often the most important aspect in the successful delivery of any project. Since our switch to remote working at the start of the pandemic, we’ve been faced with the challenge of using our project management tools in different ways to ensure that the quality of our communication and collaboration doesn’t suffer.
COVID-19 has turned our lives upside down. Just a few weeks ago, companies had to quickly transition all employees to work remotely. As businesses and people are gradually adjusting to the new circumstances and realising the benefits of working from home, many predict that this operation model is here to stay far beyond the crisis.
Internship is a two-way street. Mentoring young people is an empowering experience for the employees, while for interns, it's an excellent opportunity to learn new skills and get a taste of a potential career.
Successful software delivery is based on careful planning, accurate estimation and a good understanding of what is in and out of scope. In traditional project management, projects are broken into work packages and assigned to specialists for sizing and estimation. These packages are in turn broken up into progressively smaller modules to get increasingly more accurate sizing. After that, all the sizings are rolled up, and a project plan is reviewed and monitored.
"Your most unhappy customers are the greatest source of learning."
quote from a wise Customer Service Manager
Which type of customer are you?
Imagine you receive an email with the subject "Customer Satisfaction Survey". How does it make you feel? How do you respond?
Imagine a typical scrum scene - the team gathers around the board for the daily standup, one of the team members gives his/her overview of the matters at hand. Things seem to be going well until somebody mentions a dreaded 'blocker' word. Suddenly the team panics, the ears of the scrum master perk up, and madness ensues.
Not all user stories are equal. Some may be larger and more complicated than others. The challenge in agile delivery is to keep stories at the right size. That way, they are easily understood and delivered. Those that are too large pose a risk. Wherever possible, you should break them down into smaller, more manageable pieces. In this blog, I will explore factors that might lead to user stories being too 'large'?