Whatever stage your product development is currently in, here are some ideas for incorporating user feedback.
Continuous improvement is essential in our constantly evolving technological world. Having a growth mindset helps to foster and facilitate improvements both personally, and within a team.
Centare employees are always eager to learn more and improve. Here's what's been keeping our leadership team inspired.
In other engineering disciplines, engineers are often required to undergo a licensing process. As software becomes responsible for everything from heart monitors to stock exchanges to missle guidance systems, should software developers take up licensing in their profession?
The massive and rapid growth of the open-source community has made our lives a lot easier, saving us time and effort with a plethora of freely available packages.
While everyone has a favorite IDE, we all have less important, but still extremely helpful little tools. These tools won't make a project successful on their own, but can make a job feel a lot smoother. We asked some of our developers what their little lifesaver tools are.
Spend too little time on beautification, and the stakeholders might not like it. Spend too much time, and the stakeholders might be disappointed by how little got done.
Exploratory testing is a staple activity for experienced QA professionals, yet it is sometimes difficult to quantify the value of and need for it to a stakeholder or someone not integrated on a development team. I reached out to our team members to get their perspective on how they perform exploratory testing and its value.
We aim to have stakeholders fully engaged throughout the duration of the project but often this is a challenge. I have some tips and also asked other product owners from our organization to provide their tools and techniques for stakeholder involvement and how to create a partnership for product success.
There are many strategies and approaches to bug reporting and tracking, but how do they hold up within an agile process? Agile facilitates close-knit teams and constant communication, but does that change the way that bugs should be handled?
The final event in the Sprint cycle is the Sprint Retrospective meeting. The purpose of this meeting is for the team to reflect on and inspect all aspects of the last sprint and create a plan for improving during the next sprint. From communication and relationships, to processes and tools, any topic that impacted the team is up for inspection and consideration. Effective retrospectives can have a massive influence on the velocity of a team over the course of a project - but how do you make sure your retrospective meetings are effective?
Too much technical debt will kill your momentum, but most technical debt is invisible to users. This presents a conundrum. How do you pay off technical debt, which is usually invisible, while also delivering useful features to users?
The fourth Scrum Event is the Sprint Review meeting. Review meetings are time-boxed and are meant to be a platform for the team to demonstrate working software to the stakeholders and receive feedback. I reached out to our team to get their guidance on how to have a successful and valuable sprint review.
Backlog Refinement meetings are meant to further prepare and curate upcoming backlog items for the next sprint. This high-level description of “Refinement” can mean a lot of different things. I reached out to our team to get their perspectives on what value backlog refinement provides to the team.
The second event during an Agile Sprint is the Daily Scrum. The daily scrum (sometimes colloquially called the 'standup' meeting) is a recurring, 15-minute meeting that is held by the team and is for the team. The sole reason for having this meeting every day is to empower the team to be successful.
The by-the-book purpose of Sprint Planning is for the Product Owner to describe the highest priority features to the team and give the rest of the Development Team a forum to ask questions. The team should come out of the planning meeting with a sprint goal and a sprint backlog. While these two items are very tangible, I have found many other valuable takeaways from sprint planning meetings.
When a peer does something great there are many ways to acknowledge their behavior
Typically we are showing our development teams and stakeholders the final designs and nothing about HOW that design came to be and it is met with skepticism. Is it possible to get automatic design buy-in from your development team?
What is your preferred source code branching strategy, and why? Our experts weigh in.
Knowing that there are many QA tools out there, I reached out to our QA team to see if they had any favorite tools they would recommend considering and why.
Each of the Product Owners who participated in the Product Owner panel on April 17th share some of their thoughts about the experience.
There is a lot of confusion in our industry about what an Agile Coach does and how they add value to on organization. It takes a lot to be an Agile Coach and a lot of their work can sometimes be subtle and far reaching.
While I can appreciate the idea of setting a lofty goal then promoting and pursuing it with decisive enthusiasm - my viewpoint has evolved to question setting a global edict or goal without consideration for the details of the individual project.
What considerations should be made when deciding to automate your test cases? We reached out to our QA experts to get their take on when and why to automate tests.
Public speaking is an important skill in the working world and it is often one of the most feared skills to get started working on. We reached out to our team for some encouragement and advice on how getting out there and speaking at an event can help you.
We asked our experts to help illuminate some of the bad habits that someone new to this role might encounter.