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
I cover topics for Technologists from CIOs to Developers - agile development, agile portfolio management, leadership, business intelligence, big data, startups, social networking, SaaS, content management, media, enterprise 2.0 No Scrum Master? How should Enterprises fill the Scrum Master Role? Tuesday, November 03, 2009.
I cover topics for Technologists from CIOs to Developers - agile development, agile portfolio management, leadership, business intelligence, big data, startups, social networking, SaaS, content management, media, enterprise 2.0 Who should be the scrum master? software development. (51). webdevelopment. (12).
Maturing agile development without a maturity model. In many cases, maturity models are just tools used by consultants and sales engineers selling expensive ‘how to’ guides to senior IT executives. Next post: SCRUM for Process Maturity. software development. (51). webdevelopment. (12).
The company’s IT organization replaced some waterfall processes with iterative Agile processes managed in scrums and implemented in sprints. But a major focus is also on reskilling – not only to acquire tech skills, but also to develop business skills and what Lowell refers to as “human” skills.
Labels: agile software development , business exchange , product management. 1 comment: Korayem 11:07 AM I work as a consultant with some scrum teams and i am glad to read your insights. software development. (51). webdevelopment. (12). product management. (26). project management. (50). social media. (3).
We organize all of the trending information in your field so you don't have to. Join 83,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