This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
From the long list of observation, heuristics, and mental models in psychology, organizational design, or softwareengineering, I pick six “agile laws” that seem to be particularly relevant in this area of distributed agile teams: Conway’s Law. Agile Laws: Conway, Brooks, Hackman, Goodhart, Larman, and Parkinson. Brooks’s Law.
The idea has been around for several years: design the teams according to the product requirements and give them autonomy to create the best possible solution from both a value proposition and an organizational sustainability perspective. Eli Goldratt: “ Tell me how you measure me and I will tell you how I will behave.
Ultimately, the role of (top) management is to keep their business healthy and economically sustainable. Each comes with creative exercises that we developed in our work with Scrum and Agile teams. SCRUM and productivity in software projects: a systematic literature review. Journal of systems and software , 81 (6), 961–971.
This can help teams avoid burnout and ensure that everyone is working at a sustainable pace. Hold regular team building activities via team lunches, happy hours, or team-building exercises. By analyzing data and using historical project performance metrics, management can set realistic deadlines and allocate resources accordingly.
In the 1960s, it was considered a baseline good practice in softwareengineering to test your code as you wrote it. The pioneers of software development in that era were proponents of various levels of testing; some advocated “unit” testing and some didn’t, but all recognized the importance of testing code.
Using the value stream mapping approach, everyone from softwareengineers and developers to project managers can refresh their knowledge of how workflows can or should go. This means any action or activity considered necessary to sustain a business, even though it does not contribute to its customer requirements.
LinkedIn data indicates a massive global demand for green skills like supply chain decarbonization, sustainable management, and environmental protection. Those who do often have to borrow money from other buckets like L&D, which isnt sustainable. But not everyone can compete. Corporate inertia.
We organize all of the trending information in your field so you don't have to. Join 100,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content