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
Everybody’s talking about agile softwaredevelopment these days: project managers, softwaredevelopers, IT directors, small startups and big corporations. What is Agile SoftwareDevelopment? Agile softwaredevelopment is an approach that promotes delivering value quickly to the customer.
We’ll go through some of the most popular project management methodologies, which are applied in many sectors such as softwaredevelopment, R&D and product development. When to Use It: The practice originated in softwaredevelopment and works well in that culture. Top 10 Project Management Methodologies.
The most successful students also include reading a range of PMI-ACP books in their exam prep, as well as a training course, just as that little bit of extra comfort. It’s also useful to have books to carry around with you for reference when you can’t access your training materials. Alternatively, choose books that fill in your gaps.
Kanban history has informed everything from manufacturing to softwaredevelopment. For those unsure what kanban is, we’ll first explain the kanban system and then go into kanban history from its development to its uses in manufacturing, project management and softwaredevelopment.
What I learned from this book is The purpose (goal) of Lean is to get to the shortest sustainable lead time with quality and value. Lean SoftwareDevelopment As Scrum is typically utilized by Software Engineering teams, I will shift the focus to Lean SoftwareDevelopment. The acronym is DEBASED.
As the project manager, it’s good practice to book out time to spend elaborating the next iteration of the plan as you get closer to the relevant time frame because people’s calendars get booked up. Hold consistent, regular planning sessions. Use this approach to planning and schedule in waves where it makes sense to do so.
And one of the areas is team agility – how does a team organise itself to frequently deliver small increments of software? A lot of thought went into these questions, including multiple reviews from other softwaredevelopers, team leaders and project managers. So, should teams always implement methods 100% by-the-book?
This one is for softwaredevelopers. Ron Jeffries has an article describing how fundamental refactoring is in the basic professional practice of a softwaredeveloper. Softwaredevelopment techniques are not the responsibility of the project manager, customer, Product Owner, or any other non-technical stakeholder.
Normally I take lots of notes when I’m reading books for review. I’m seeing this more and more in project management books (I like to think I started a trend !) There is a logical flow to the book. The bottom line is that if you work with projects you need this book on your shelf. It’s the book I wish I had written.
The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and softwaredevelopment teams. Scrum is part of agile softwaredevelopment and teams practicing agile. What Is the Scrum Methodology? Scrum Values.
Unlike me, who went on maternity leave just before a two-year softwaredevelopment project went live (that was some handover). Book yourself out so that your diary is full and no one tries to book you to attend a sneaky meeting. Again, this is all about managing expectations. This is your time to catch up.
In this post: start a book club for developers. Gatherings of our book club at NowOnline often looked like this; people gathered in one of our meeting rooms. Or on the floor upstairs, amid the desks of the Development Teams. Pick a book for developers to start with. Recommended books.
For example, some organizations may have very high-level criteria in their Definition of Done, such as the requirement for all Scrum teams to use software that is currently supported or requirements specifying what level of security checks must be performed on any new softwaredevelopment.
I caught up with Mark so that he could explain that interesting title and talk more about the book. There are many examples in the book, but I think the best examples come from those that decide to transform their project delivery process, rather than rescue a specific project. But what is visual project management?
From Softwaredevelopment to enterprise-level transformations, Agile has become the cornerstone of modern work, empowering teams to be flexible, iterative, and customer-focused. They drive meaningful change through their books, talks, social platforms, and real-world implementations.
Software projects can be complex and unpredictable, which is why you need a solid grasp of the softwaredevelopment lifecycle, a suitable framework, and a powerful work management platform at your disposal. This makes communication and efficiency even more critical to project success.
This is where product developmentbooks can help. As I was working with clients experiencing the transition from projects to products I was lucky to engage with several authors of product-first, #NoProjects books and chat about the challenge areas and potential solutions. Allan Kelly, Software Strategy Ltd.; October 2018.
Elizabeth is also a prolific author, having published seven books on project and change management. Her book, Shortcuts to Success: Project Management in the Real World , was shortlisted for the prestigious Management Book of the Year Award in 2014, further cementing her status as an influential voice in the field.
You have to create a key for your project – the sample project I created was about writing my next book, so I chose BOOK. Now all my activities are prefaced with BOOK. Backlog started life as a tool for softwaredevelopers, and it shows. However, two things threw me off balance at the beginning. Using the Wiki.
The scrum methodology has been around since the mid-1980s and has been a core sub-methodology of agile since 2001 when Ken Schwaber and Mike Beedle wrote the book on it: Agile SoftwareDevelopment with Scrum. That hasn’t stopped practitioners from using scrum in varying industries, from retail logistics to event planning.
And many project managers still think it is something that only applies to softwaredevelopment. Iterative and incremental softwaredevelopment methods go back as early as 1957 – and maybe earlier. Evolutionary project management and adaptive softwaredevelopment started in earnest in the early 1970s.
A good project management book. the truth is that project management books are a more in-depth way to get inside the minds of the best managers out there. We combed through best-seller lists, spoke with veteran PMs, and read a ton to put together this list of the best project management books for upgrading your career in 2020.
Have you ever heard of a T-shaped developer? It’s a common phrase used in softwaredevelopment where the developer has broad experience in their role but is also profoundly skilled in one specific area. The horizontal bar of the “T” represents their broader skill set.
Book quality checks Now you know what project quality measures you are trying to hit, book some quality checks in. Also, if you have internal auditors or a Quality Assurance function, or someone in the PMO who can do an informal (or formal) project review, book that in as well. The options are: Once (i.e.
Jennifer wrote a book about archetypes called Optimizing Your Thinking , in which she describes eight types of people. For instance, there was a softwaredeveloper on my team, Wayne, and when he got stressed, he loved to play golf. I personally wrote this book called “Optimize Your Thinking.”
If you have come across the book Reinventing Organizations by F r ederic Laloux you would know that there are many different ways an organization can be structured. One of the principles from Manifesto for Agile SoftwareDevelopment states Build projects around motivated individuals.
Behavior-Driven Development (BDD) is a well-known practice for collaboration and teams use it to bridge the gap between product management and the softwaredevelopment team. It is also very popular among quality engineers to develop test automation frameworks. And Provide option to book flight.
Six Sigma has proven itself adept at working with collaborative teams since the year 2000 when it developed into Lean Six Sigma. This was first codified in the book Leaning into Six Sigma: The Path to Integration of Lean Enterprise and Six Sigma by Barbara Wheat, Chuck Mills and Mike Carnell. Lean Six Sigma. Six Sigma and Agile.
While Greg’s book provides a lot of insights, there’s one line which really resonates with me: “ If it isn’t a clear yes , then it’s a clear no.” Minimal sufficiency should be our goal when expending effort on anything which doesn’t create business value for our stakeholders.
A capacity planning tool is softwaredeveloped to assist organizations in allocating and managing their resources more effectively. Other Features Resource scheduling Resource management Leave management Project scheduling Equipment management Timesheet Meeting room booking system Project forecasting reports 4.
This realization was not just an operational shift but a philosophical one, emphasizing the importance of adaptability, collaboration, and a people-first approach in the ever-evolving landscape of softwaredevelopment. NKDAgility can help! At NKDAgility, we're transforming how Agile and Scrum training is delivered. Just ask!
Have you ever heard of a T-shaped developer? It’s a common phrase used in softwaredevelopment where the developer has broad experience in their role but is also profoundly skilled in one specific area. This is a guest post from Charlie Davidson. Charlie Davidson. An extreme example could be Jeff Sutherland.
In fact, softwaredevelopment and project management are like two peas in a pod known as softwaredevelopment project management. Every implementation of the project management processes is different and the same can be said for softwaredevelopment project management.
He literally wrote the book about it, It’s All in How You Slice It , which came out in 2005. The idea of a user story as it applies here comes from softwaredevelopment and product management. A user story is an informal description of one or more software features, written from the perspective of an end user in plain English.
But, the reality is that over the last 20+ years of the Agile Manifesto, the context, use, and experience with agile provides some evidence that there is a fundamental attribution error concerning the approach to Agile Softwaredevelopment and its execution. It can be a challenging leadership problem and problematic to resolve.
For example, I can’t do more than one book review for this blog at a time, so my workload would only show one at a time. This is my ‘go to’ book for understanding agile, although it is written predominately with a softwaredevelopment environment in mind. (Does it work like this in real life? How Progress Is Measured.
Over-planning not only wastes resources but also becomes quickly outdated in the fast-paced world of softwaredevelopment. The alternative, a more minimal and flexible approach, not only aligns better with Agile principles but also with the realities of softwaredevelopment. NKDAgility can help!
In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM SoftwareDevelopment Process” by Ken Schwaber (1995, 1996). The book “Agile SoftwareDevelopment with Scrum” by Ken Schwaber and Mike Beedle (2002).
Thought-leaders often have a stake in promoting certain beliefs, so as to bring people to their classes, books, or products. There are dozens of high-quality academic works to draw from, there are dozens of academic journals dedicated to (agile) softwaredevelopment (ASD) and change management. All these sources offer evidence.
Given this, I felt it was somewhat timely when I was invited to review Jonathan Sapir’s new book, Thriving at the Edge of Chaos – Managing Projects as Complex Adaptive Systems. A number of the principles he covers in the first half of the book will resonate with both agilists and anti-fragilists including: Self-organization.
Let’s say a softwaredevelopment team recognizes that they need to improve their code quality and to do this there are many options available. Coding standards, coding reviews, non-solo coding, test-first development, and automated code quality tools are just a few choices.
First, in a blog series about the upcoming book: Creating Agile Organizations - A Systemic Approach by Cesario Ramos & Ilia Pavlichenko. ?. The critical point is that your software must be soft enough to change it quickly, at a low cost, and validate if it delivers what is expected.
wrote The Mythical Man Month, he provided project managers with the valuable caution which later was named Brooks’ Law: “ Adding manpower to a late software project makes it later “ While there are always exceptions, this statement is generally true. as well as a number of other online book stores).
Richard is the author of two books: High-Performance Teams: The Foundations. Richard created and teaches the course Agile SoftwareDevelopment at Harvard University, and he co-teaches the Spark! Richard Kasperowski is an author, teacher, speaker, and coach focused on team building and high-performance teams.
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