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
In my work week, this has meant a change to Agile Scrum as a development methodology. And along with that comes a number of learnings that are worth repeating here on my blog. We used some principles of Agile softwaredevelopment Agile isn't entirely new. Our approach before this had been semi-agile.
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.
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.
Which softwaredevelopment methodology is best? As a CIO I suspect that you are well aware that there are a number of different ways that your IT teams can go about developingsoftware (and doing a lot of other things). Each agile cycle focuses on continuous improvement in the development of a product or service.
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? SDJ is the oldest magazine for developers in Poland.
But to be a agile family with a scrum board, and family retrospectives? Labels: about me , agile softwaredevelopment , innovation. agile softwaredevelopment. (56). offshore development. (6). softwaredevelopment. (51). software qa. (8). web development. (12). Blog Archive.
Enterprise Agile Development - Why you still need Project Managers. Ive been asked lately about the role of project managers on agile or SCRUM teams. Some specifics: Scrum and agile are very team and inward facing. Labels: agile softwaredevelopment , project management. hapi blogging. software qa. (8).
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 Top 7 Ingredients to Establishing an Agile Development Practice. agile softwaredevelopment. (56).
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 Four Phases of Maturing Enterprise Agile Development. Also, see my Top Ten Thoughts for SCRUM Newbies.
I then discussed how BusinessWeek moved to an agile development process (specifically, SCRUM), to build its newest product, the Business Exchange. I will get the slides out eventually, but first Im going to blog on a few related subjects. agile softwaredevelopment. (56). offshore development. (6).
Agile proponents did themselves a favor adopting the generic agile development to represent processes like SCRUM, Extreme Programming, etc. Do your technology choices easy lend themselves to agile (think fast) development cycles? Also, agile practitioners (product owners, scrum masters, developers, etc.)
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 softwaredevelopment life cycle. My most popular post was on the Top 5 Attributes of Talented Agile Developers. agile softwaredevelopment. (56). offshore development. (6).
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 softwaredevelopment , cio , it management , project management. agile softwaredevelopment. (56). offshore development. (6).
My favorite business topics include CIO , Agile SoftwareDevelopment , Enterprise 2.0 , Open Source Software and Social Networking. Labels: about me , agile softwaredevelopment , business exchange , in the news , media and publishing , web 2.0. agile softwaredevelopment. (56). software qa. (8).
Agile practices (SCRUM, XP , etc.) When we started TripConnect , we followed agile methodologies even though the first version of the product was developed offshore. Those priorities pretty much set us down a path of agile development. Labels: about me , agile softwaredevelopment , enterprise 2.0 , it management , startup cto.
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. agile softwaredevelopment. (56). offshore development. (6). about me.
So if you are buying into my methodology, the next step the CIO must determine is how to introduce an agile development life cycle to both the Technology and the Business organizations. Now my assumption is that if youre reading this blog or post, you know a fair amount about agile development and planning. software qa. (8).
Labels: agile softwaredevelopment , product management , project management. agile softwaredevelopment. (56). offshore development. (6). softwaredevelopment. (51). software qa. (8). web development. (12). Mark Logic CEO Blog. Blog Archive. Ill elaborate in another post.
If you’re lucky they’ll tell you about their software stack and then throw in a bit about their softwaredevelopment life cycle. agile softwaredevelopment. (56). offshore development. (6). softwaredevelopment. (51). software qa. (8). web development. (12).
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. Great articles posted at the Business Exchange Agile SoftwareDevelopment topic. Labels: agile softwaredevelopment , product management.
Its a smart team, but they are immediately jumping into solving problems and developing artifacts. 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. agile softwaredevelopment. (56).
From Iterative to Agile Once we optimized around iterative delivery, there was a collective effort between members of my team as well as our offshore partner to move to agile development. If youre practicing SCRUM, make key members of your teams have some basic training. agile softwaredevelopment. (56). software qa. (8).
Below is an incomplete list of some things the Business needs to manage when working with an Agile softwaredevelopment team 1) Expect to spend a lot of time with the technologists! - Labels: agile softwaredevelopment , business exchange , product management. agile softwaredevelopment. (56). software qa.
Now theres nothing wrong with the article or some of the concepts, but I feel compelled to throw in my two cents on maturity models in general and especially applied to agile softwaredevelopment. In general, Ive only seen maturity models used in one way - to sell enterprise executives either software or services. software qa.
agile softwaredevelopment. (56). offshore development. (6). softwaredevelopment. (51). software qa. (8). web development. (12). Mark Logic CEO Blog. Blog Archive. Top Ten Thoughts for SCRUM Newbies. Social, Agile, Transformation Pages. My Publications & Awards. about me. (33).
The research firm also believes that softwaredevelopment organizations should incorporate coding standards such as CERT C and utilize the Common Weakness Enumeration (CWE) database. Companies like Programming Research, Critical Software, or Jama Software offer tools to assist with static analysis of code against these standards.
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