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
No Scrum Master? How should Enterprises fill the Scrum Master Role? I field this question very often and especially from members of technology organizations where agile and scrum in particular is being introduced top down from Management. Do you need a business analyst and a projectmanager?
Top Ten Thoughts for SCRUM Newbies. My colleagues and I from BusinessWeek gave a presentation last week covering our agile planning and development process and ended with an intro to SCRUM by @silviogalea. Roughly the same time, @jurgenappelo posted an excellent, easy to follow slideshare on The Zen of SCRUM 1.0.
Enterprise Agile Development - Why you still need ProjectManagers. Ive been asked lately about the role of projectmanagers on agile or SCRUM teams. While projectmanagers can perform specific roles within the team, they often perform functions that go beyond the scope of an agile teams direct responsibilities.
Arooni, along with his CIO counterparts, have made a variety of structural changes and initiated a range of best practices to ensure a successful transition away from legacy-style projectmanagement to an IT operating model architected around product centricity. Establishing technology and business owners also drives collaboration.
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? crisis management. (3). it management. (34). Newer Post.
But we managed priority changes and integration issues to get a product out. I then saw this post Agile ProjectManagement: Lessons Learned at Google that I found on the Agile Software Development topic at Business Exchange that gave me some new ideas on scaling agile. crisis management. (3). it management. (34).
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 Labels: agile software development , projectmanagement , software development , web development.
Most technology departments have projectmanagers who often are (and should be in my opinion) technical and are also good business analysts. These projectmanagers should be spending a good deal of their time understanding the business requirements and overseeing the schedule and deliverables of the technology team.
I know of companies that have used agile methodologies outside of technology including marketing, construction, and operations. But to be a agile family with a scrum board, and family retrospectives? crisis management. (3). it management. (34). product management. (26). projectmanagement. (50).
Agile practices (SCRUM, XP , etc.) Can you imagine a Startup CTO telling investors that they would spend two months on documentation and three months on development work before demoing a first version of software? We didnt spend a lot of time discussing SCRUM or other approaches internally or with executives. it management. (34).
startups challenged, short runway on funding, needs to become cash positive Many technology options for web 2.0, I then discussed how BusinessWeek moved to an agile development process (specifically, SCRUM), to build its newest product, the Business Exchange. crisis management. (3). it management. (34). startup cto. (19).
Agile proponents did themselves a favor adopting the generic agile development to represent processes like SCRUM, Extreme Programming, etc. Enterprises are big, decentralized, with legacy technologies, standards processes, and governance concerns. Are you open to a different approach to managing and measuring projects?
Measuring actual costs turns out to be an easier process assuming that you have a tool to manage the backlog and a scrum master running daily standups. Labels: agile planning , agile software development , cio , it management , projectmanagement. crisis management. (3). it management. (34).
Recognize that process is always in a state of flux and improvement, so when improvements are needed or opportunities identified use an agile / SCRUM process to schedule, commit, and measure improvements. Next post: SCRUM for Process Maturity. crisis management. (3). it management. (34). product management. (26).
Looking back to 2008, I shifted this blog from covering startups and issues for CTOs (re: Startup CTO ) and covered a lot about the agile software development life cycle. I also covered some practical matters on when to use (and not use) pair programming , a bit on the Scrum Master role , and on story writing vs requirements docs.
Make sure the business project is appropriate (I will cover in a future post) and make sure its sponsors are willing to participate in the program. Your coach will probably have a program, but heres one on How to Implement Scrum in 10 Easy Steps. Also, see my Top Ten Thoughts for SCRUM Newbies. crisis management. (3).
This is especially true with agile practices since the choice of what processes to establish and areas to mature needs to fit a business need and priority and these improvements can be managed through the scrum process. Labels: agile software development , projectmanagement. crisis management. (3). startup cto. (19).
I'll always remember the Business Exchange team as being one of the best Scrum teams I have worked with. crisis management. (3). it management. (34). product management. (26). projectmanagement. (50). startup cto. (19). Strategic Technology. ► January. (3). No Scrum Master?
5) Help the team make it successful - Make sure all team members have a basic foundation in an agile (probably scrum) process. I highly recommend training and ideally an agile coach if you can afford it, but at minimum make sure you have a team lead (scrum master.) whos been through a successful agile project. it management. (34).
The problem is, using agile process (scrum specifically) for planning, problem solving, developing a strategy, documenting an architecture requires some discipline and thinking a little differently. Labels: agile planning , cio , it management , projectmanagement. technologies. crisis management. (3).
If youre practicing SCRUM, make key members of your teams have some basic training. When recruiting new members, look for people with experience on agile projects Make sure your offshore team members have some understanding of the business, product, and even competition before going agile. crisis management. (3). startup cto. (19).
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 For those of you who don’t know, I was CTO of a SaaS vendor a number of years ago. about me. (33).
One good way to insure a smooth transition is to learn the process either through participation, taking a training class, and ideally applying agile/SCRUM as a business process. crisis management. (3). it management. (34). product management. (26). projectmanagement. (50). startup cto. (19).
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. crisis management. (3). it management. (34). product management. (26). projectmanagement. (50). startup cto. (19).
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