InfoQ Homepage Feedback Content on InfoQ
-
Using Retrospectives for Personal Improvement
Agile retrospectives are used by teams to improve their performance, by reflecting on the way of working and defining improvement actions. But retrospectives can also be used for personal improvement, additional to or as a replacement of performance appraisals. Such retrospectives can be done as a one-on-one by a manager and an employee, individually by an employee, or in a team.
-
Using Feedback Techniques for the gov.uk Website
Jake Benilov will give a talk on September 27 at Agile Tour Brussels about feedback techniques used for making gov.uk. InfoQ did an interview with Jake about using the feedback techniques and how the team applies lean startup with minimum viable products to do user research.
-
How to Use Feedback with Performance Appraisals for Agile Enterprises
When enterprises implement agile ways of working, questions can arise if changes are needed in the way performance appraisals are being done? Several authors have suggestions on how you can use feedback next or as a replacement for existing appraisal processes, to improve the performance of individuals and teams.
-
Pivoting when Using Lean Startup for Product Development
There are different types of pivots possible in lean startup, which help you to decide whether to persevere or pivot during product development. They each with their own purpose and ways to use them. Let’s explore some of them to see when and how you can pivot? Or maybe have to decide that it’s better to quit?
-
Experiences from Educational Technology Startups
Educational technology is developing itself, and startups are entering markets with new apps and creative commons content. Speakers shared their experiences on education and gaming and finding the right fit for an EdTech startup, at the GOTO Amsterdam 2013 conference.
-
Feedback, Non-Feedback and Uncalled Feedback
The importance of feedback in Agile development is paramount. Feedback is built into every aspect of the methodology ranging from unit tests, continuous integration, daily standup, retrospectives to end of sprint demos. In-spite of all this, are there still some feedback loops which remain incomplete?
-
The Importance of Agile Feedback Loops
Several members of the Agile community emphasize the importance of feedback loops in the effectiveness of Agile development processes.
-
Learning from the creative industries - consistency to build trust
This is the first in a series of discussions looking at factors that enable teams to be successful. This post reports on a recent Wired magazine article that looks at the creative process in use at Pixar Animation Studios and how their process encourages team formation, long-term relationships and trust in a “safe to fail” environment.
-
Feedback and Feedfoward: Best of Both Worlds
Feedback is a situation in which an output from an event of the past has a potential relevance in the future. Agile places a lot of importance on soliciting and providing feedback with every step in order to build a quality product. On the other hand Feedforward is, to give someone suggestions for the future and provide help in terms of future direction.
-
Giving and Receiving Effective Feedback
On Monday at the first day of Agile 2009 Liz Keogh ran a workshop and Effective Feedback.
-
Top InfoQ News and Exclusive Content for 2008
Looking back at the year that is coming to its conclusion, we wanted to have a retrospective and find out which were the most read news and exclusive content items during 2008. We compiled a list containing top 5 news for each community and top 3 exclusive content items for each type: articles, interviews and presentations. This list considers the number of unique readers for each news.
-
Presentation: Jim McCarthy and 11 Commitments For a Shared Vision
In this presentation filmed during Agile 2008, Jim McCarthy talks about 11 commitments team members should adhere to if they want to achieve a state of shared vision. Such a state empowers a team to reach their full potential and ultimately attain greatness.
-
Opinions: Why Most Social Software Fail and how to Avoid it
According to Clay Shirky, the success key for social software is “a brutally simple mental model [...] shared by all users”. Referring to it as Shirky’s law, Michael Nielsen analyzes why programmers often fail to obey it. His arguments as well as the discussion that has followed provide interesting insights into pitfalls that need to be avoided for building successful social applications.
-
Presentation: Martin Fowler and Dan North Talk Over the Yawning Crevasse of Doom
In this presentation filmed during QCon London 2007, Martin Fowler and Dan North talk about the communication gap existing between the developers and the customers or users. Closing this gap is extremely important in order to create successful software.