Until recently, many jobs simply didn’t exist. Take a wind farm engineer, for example, or an e-learning course developer. The rapidly emerging technology creates new occupations and changes the way people work.There is also a good deal of jobs which are not new, but remain overshadowed and blended into various other occupations.
Surprisingly, project management wasn’t recognized as a distinct occupation until recent time – at least, not in the U.S. Department of Labor’s official statistics.
2017 has been a remarkable year for digital transformation. Machine learning, AI and Big Data are some of the technologies that dominated 2017. Advancements and enhancements in these technologies will continue for coming years – but what can we predict for the IT industry in 2018? Will AI prove to be a job creator or a destroyer? Will global tech-giants have to self-disrupt to shape their new leadership opportunity? Will 2018 prove to be a slow death for IT specialists?
Today, tech innovations arrive faster than most of the enterprises can cope up with. All too often, before one innovation is embraced and implemented, other two appear on the horizon. To cope with these endless innovations, CIO’s of the enterprises must pursue and excel the role of a business strategist first and secondly as a technologist, thereby developing an appropriate pace for the digital transformation.
If you’ve set foot in the world of software you’ve probably heard the word "Agile" more times than you can count. You may have heard this word associated with constant collaboration, continuous delivery, releasing faster, adapting constantly, or any other "features of being Agile." It is clear that teams who are involved in all phases of the software development lifecycle are starting to adopt this "Agile" methodology as its increase in popularity continues to grow at a fast rate.
Earlier this year, over 5,000 professionals in Software Development, QA, and Testing responded to the SmartBear 2017 State of Software Testing Survey, and one of the most intriguing areas of the survey results was on this idea of being "Agile." Through this survey, we asked teams to categorize their development styles as either Agile, DevOps, Waterfall, Dependent on the Project, or Other and some results we found were expected while others were surprising.
Agile brings a lot of benefits, provided it is used in the right way. I thought I’d share my experiences. Feel free to comment with your thoughts and experiences!
Agility (the ability to move quickly and easily) helps in making software development lightweight, easy, simple, minimizing the process and overheads, allowing you to meet and beat the market.
As a Product Owner, you are responsible for Product Backlog management, stakeholder management, and forecasting. Therefore, you will probably use a variety of tools and techniques to track progress, manage expectations, and keep people informed. One of the tools that may come in handy for you is a product roadmap. Applying product roadmaps effectively can be challenging, however. The concept of a product roadmap is that it is a high-level, strategic plan, that describes the likely development of the product over a given period of time. The roadmap should support the products’ purpose and vision and it helps the Product Owners to keep their stakeholders aligned. The roadmap also makes it easier to coordinate the development of different products and it fosters transparency in order to manage customer expectations.
In a lot of organizations, I see that Product Owners are focused mostly on developing features and therefore, a lot of roadmaps are also dominated by features and functionalities to be delivered. The disadvantage of focusing on features too much is that there are always too many features that would add value, therefore creating a lack of focus on the vision and goals. By focusing on the features too much, the roadmap will turn into an overloaded product backlog, instead of a high-level, strategic plan for the products’ future development.
Here I am sitting in my hotel room while looking at my half-empty wine glass and the stars outside while preparing for my last Professional Scrum Master (PSM) class for the year 2017 and pondering about all of the classes I have facilitated over this year. PSM has been a transformational course for me because it has changed me by seeing how it has changed the life of many of my students.
Starting from the end of 2017, Scrum.org has put more emphasize on servant-leadership for Scrum Masters. After all, the Scrum Guide explained that the Scrum Master is the servant leader of the Scrum team and the organization to which she belongs.
To make great software, you need the best developer tools—or at least they’ll make your life a lot easier! At Axosoft, we pride ourselves on building great tools like Axosoft, a Scrum project management software, and GitKraken, a cross-platform Git GUI client. There are a lot of other great tools we like to use internally, but we wanted to know what dev tools are being most widely used in the industry.
So, to find out, we asked our community to tweet their top 5 dev tools using #MustHaveDevTools. There were over 1,000 tweets—twice as many as last year!
I get a lot of reader questions about freelancing. People interested in freelance web development or freelance mobile development or what have you. I applaud the desire to go free agent, and I think you should do it. But I think you get a lot of bad advice about how to do it. Bad advice at a philosophical level, that is.
Today I’m not answering a specific reader question, though. Instead, I’m just going to talk about going freelance. I did this years ago and have had a good run. But I really wish I knew then what I know now. Hopefully, I can help you get to joy a lot quicker and in less roundabout fashion than I did.
Source : https://dzone.com/articles/be-a-freelance-developer-youre-asking-the-wrong-qu?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fagile
Project management as a concept can be extended to anything from running an enterprise to following a personal to-do-list. The idea remains the same throughout all of these activities and it’s only the scale that changes.
After working on Kanban Tool and with Kanban as our sole PM tool for a decade, we’ve come to associate project management with visual management. Unless the process is visually available and readable at a glance, no-one has a full view of what is going on.
This post is based on a talk that Gunnar Wagenknecht and I delivered at the Open Source Leadership Summit 2017 and Devoxx US 2017. This content was recently published in the All Eyes on Open Source issue of JAX Magazine.
Running an open source project is easy. All you have to do is make your source code available and you’re open source, right? Well, maybe. Ultimately, whether or not an open source project is successful depends on your definition of success. Regardless of your definition, creating an open source project can be a lot of work. If you have goals regarding adoption, for example, then you need to be prepared to invest. While open source software is “free as in beer”, it’s not really free: time and energy are valuable resources and these valuable resources need to be invested in the project.
