Skip to content

Feed aggregator

Link: Transitioning from Waterfall to Agile

Learn more about transforming people, process and culture with the Real Agility Program

I have yet to find a better article than this one on transitioning from Waterfall to Agile.

Transitioning From Waterfall to Agile

By Sanjay Zalavadia

Agile is designed to promote positive and functioning relationships among team members, enabling self-administered teams and team processes that address the continual consumer demand for updates and the fluctuating levels of software consumption. Teams integrate multi-talented resources into cross-functional process to boost production and inspire innovation.

Agile methodologies allow assessment of project direction throughout the entire software lifecycle. The strategy of regular iterations incentivize teams to produce potentially shippable output at the end of each incremental build, providing immediate opportunities to redirect objectives for quicker and more continuous delivery. In this way, software development can happen while requirements and analysis are occurring. Development is integrated into fact-finding through the build activity rather than strictly defined as stages of production.


Continue reading here.

Learn more about our Scrum and Agile training sessions on WorldMindware.comPlease share!

The post Link: Transitioning from Waterfall to Agile appeared first on Agile Advice.

Categories: Blogs

Skills that Developers Need to Acquire to Achieve an Agile Transformation

NetObjectives - Tue, 09/27/2016 - 15:20
Skills that Developers Need to Acquire to Achieve an Agile Transformation Amir Kolsky, Rob Neppel, and Jim Trott talk about eight essential skills that developers need to acquire to work in an Agile transformation. Some of these skills are certainly taught in university; some are not as common... but are still essential. These are essential for any professional developer. The essential skills...

[[ This is a content summary only. Visit my website for full links, other content, and more! ]]
Categories: Companies

Improve Team Collaboration by Co-creating a Team Poster

Xebia Blog - Tue, 09/27/2016 - 15:18
Do you have a scrum team consisting of individual players? Does your team know why it exists in the first place? Do the team members know eachother's personal preferences for doing the things they do? Are they aware of what they find important as a team? A Team Poster crafted by the team itself will
Categories: Companies

Ferguson Enterprises Improves Agile Transformation Success

Agile Management Blog - VersionOne - Tue, 09/27/2016 - 14:30

Highlights Easy access to reporting and visualizations to track progress Improved enterprise collaboration Accelerated transition to agile Strong partnership to ensure success  Challenges Ferguson Enterprises Inc., the largest wholesaler of commercial and residential plumbing supplies in North America, has been … Continue reading →

The post Ferguson Enterprises Improves Agile Transformation Success appeared first on The Agile Management Blog.

Categories: Companies

Ending the Nested Tree of Doom with Chained Promises

Derick Bailey - new ThoughtStream - Tue, 09/27/2016 - 13:30

Julia Jacobs recently asked a question in the WatchMeCode community slack, about some asynchronous code she wanted to clean up.

In this question, she wanted to know of good options for restructuring deeply nested promises without introducing any new libraries. Would it be possible to clean up the code and only use ES6 features?

Nested callback cleanup

It’s a common pattern and problem – the Nested Tree of Doom – not only with promises, but with JavaScript callbacks in general. 

The full question, is as follows

Hey all. Does anyone know any decent patterns for

a) async ES6 classes other than shoving everything into a native promise in a getter.

b) creating an async waterfall serialization flow with multiple functions using generators.  

I’ll create some gists with samples of the code I’m trying to refactor. I’m trying to stay away from libraries and stick with native ES6 goodness.

When I first read the question without looking at the example code, I wondered if promises were the right way to go.

Personally, I prefer the node style of callbacks as my go-to pattern for asynchronous code. Promises are definitely useful, but they are most useful in specific scenarios.

My initial response, however, was about ES6 generators.

the best way to take advantage of generators and async work is going to be with a small library [like co].

you can write your own with only a few lines of code, though

if you don’t like getters that return promises, can use a method with a callback parameter.

personally, i prefer callback methods over promises, until i have a specific use case for promises (like waiting for multiple things, only wanting to perform the action once but retrieve the value multiple times, chaining async ops, etc)

Once Julia posted her code sample, my advice quickly changed.

While I don’t reach for promises as my first choice, Julia’s scenario and code samples quickly changed my mind. 

Here is what she posted for the code in a hapi.js router:

It’s the result of two weeks of banging out a hapijs arch which parses a huge XML response from a Java API and maps it to a huge json contract with very strict corporate requirements.

Frankly, this code is darn near as beautiful an example as you can find, when it comes to nested callbacks and promises.

And I don’t mean “a beautiful mess” – I mean that Julia has written code that you dream of finding, when you are looking at restructuring.

Most of my own nested promises are garbage – closures; creating promises inside of callbacks; nested .catch and resolve statements and more of a mess than I care to show anyone.

This code is near spotlessly clean, already.

Unlike the mess that I tend to create with nested promises, the code Julia showed us is uniformly written.

It uses no closures.

It takes the results of the previous work and passes it directly to the next work, with nothing else.

And it does all of this through promises that are created by other functions.

The only thing this code really needs, is a small adjustment to remove the nested promises and turn them into chained promises.

As I noted in my response to Julia,

instead of doing `return SearchModel.get(json).then({ …` you can return the promise from `SearchModel.get` directly

`return SearchModel.get(json);`

Promises will take any return value from a `then` callback, and forward it to the next `then` for you

if the return value is a Promise itself, it will wait for that promise to resolve or reject

so the above code should be functionally the same just with less nesting

When you take the first few lines of the above code and apply this idea, it becomes this:

And this is where the magic begins.

By returning the promise from SearchModel.get, the code nesting has been reduced one level.

Apply this same pattern throughout the rest of the sample, and you reduce the nesting by one level, at each level of nesting.

The result is that there are never any nested promises!

But the magic doesn’t end here.

Reducing the nested promises is only the first steps in reorganizing this code.

I continued the example by talking about extracting named functions

if you really want to reduce this code further, extract each of those callbacks into a named function

then you can do `xml.tojsonhttpclient.get().then(transformit).then(mapit).then(…)`

This works because these functions are very clean. They take the result of the previous promise and pass it into the next promise. There’s no closures or other code, as I mentioned before.

The result of extracting the callbacks into named functions looks like this:

Now this is beautiful code!

But if we’re talking ES6, Let’s use ES6.

Shortly after posting this, there was some discussion on twitter, and Richard Livsey pointed out that ES6 arrow functions could be used with implicit returns, instead of extracting named functions.

@derickbailey great post. Another intermediate step could be to use implicit returns vs extracting functions

— Richard Livsey (@rlivsey)

September 27, 2016

With this post, he also provided an example that shows the use of arrow functions to achieve this:

The code I have above may be slightly cleaner when it comes to reading the chained promises, but this is a great option if you’re concerned about lines of code or having all those extra little functions laying around. 

The goal may not be to reduce the number of lines of code, though. 

In this scenario, the goal was to make the code easier to reason about and easier to change, not just reducing the number lines of code (though this may be an important aspect in other scenarios).

By taking what was already clean code and reorganizing it into chained promises instead of nested, the code became easier to follow.

When the functions were extracted and named, though, that’s when the code became easier to understand at a higher workflow level.

You no longer have to dive into the details of each promise’s callback to understand what happens next. Instead, you can look at the high level flow of chained promises and see a simplified name that represents what will happen next.

The code is easier to modify, as well. If you need to insert a new method, change a detail, remove a step, it’s all right there in the high level chaining. 

This type of restructuring is not always going to work, though.

When Julia brought this question to the WatchMeCode community slack, she was already in a good place. 

Most of the time when I’m looking at nested promises, I’m in much worse shape. 

If you face code that has closures around variables, re-using them between promise callbacks, for example, you’re going to run into problems.

If you have nested promises being created within the promise callbacks directly, or worse, you have nested promise chains being resolved and rejected, it can be incredibly difficult to fix.

You may find yourself in a situation where a promise chain is simply the wrong way to solve the problem.

But if you’re looking at code which is clean and concise like what Julia brought to us, or if you can move your code from where it is, to this clean and uniform state, then you should be able to take full advantage of chained promises.

The post Ending the Nested Tree of Doom with Chained Promises appeared first on

Categories: Blogs

The big Scrum Master misunderstanding

Growing Agile - Tue, 09/27/2016 - 11:00
This morning I received a Scrum Master job spec.  About 5 years ago these were really bad – essentially Project Manager jobs with a different name. They have gotten better and I’m even noticing words like collaboration and facilitation. The one I read this morning caught my attention as the opening paragraph was great and […]
Categories: Companies

Version 7 Beta 7

IceScrum - Tue, 09/27/2016 - 10:41
7.0.0-beta.7 Here comes iceScrum 7.0.0-beta.7. This version brings the “Team availability” feature back, making a new step towards a final release. It works as before, including the recent addition of the useful Sprint Burndown Chart that compares the remaining time to the remaining availability. Apart from that, this new beta also fixes a few bugs…
Categories: Open Source

Links for 2016-09-26 []

Zachariah Young - Tue, 09/27/2016 - 09:00
Categories: Blogs

The Forgotten Agile Role – the Customer

Many Agile implementations tend to focus on the roles inside an organization – the Scrum Master, Product Owner, Business Owner, Agile Team, Development Team, etc.  These are certainly important roles in identifying and creating a valuable product or service.  However, what has happened to the Customer role?  I contend the Customer is the most important role in the Agile world.  Does it seem to be missing from many of the discussions?
While not always obvious, the Customer role should be front-and-center in all Agile methods and when working in an Agile context.  You must embrace them as your business partner with the goal of building strong customer relationships and gathering their valuable feedback.  Within an Agile enterprise, while customers should be invited to Sprint Reviews or demonstrations and provide feedback, they should really be asked to provide feedback all along the product development journey from identification of an idea to delivery of customer value.
Let's remind ourselves of the importance of the customer.  A customer is someone who has a choice on what to buy and where to buy it. By purchasing your product, a customer pays you with money to help your company stay in business.  For these factors, engaging the customer is of utmost importance.  Customers are external to the company and can provide the initial ideas and feedback to validate the ideas into working products.  Or if your customer is internal, are you treating them as part of your team and are you collecting their feedback regularly?
As you look across your Agile context, are customers one of your major Agile roles within your organization?  Are they front and center?  Are customers an integral part of your Agile practice?  Are you collecting their valuable feedback regularly?  If not, it may be time to do so.  
Categories: Blogs

LeanKit’s New Speed Report

The new Speed (Beta) report has quickly become our most visited report. This improved visualization helps teams quickly...

The post LeanKit’s New Speed Report appeared first on Blog | LeanKit.

Categories: Companies

Link: The Solution That Fits Our Team

Learn more about transforming people, process and culture with the Real Agility Program

I recently came across an excellent article on how teams are taking the best of several Agile methods and combining them together into a solution which works in their specific environment.

The overview and description of the essence of Agile, Scrum and  Kanban is really helpful.

After you have a chance to read it please share your reflections in the comment section below.

Scrumban: The Solution That Fits My Team

by Serghei Rusu

Image title

If you have any issues with the methodology approach you have in your company, then you have probably heard these words already. That is our case as well. At a certain point in time, we felt like we were no longer facing the rapidly changing requirements that come from modern world business and that the software development methodology we had was pulling us back….

Continue reading the article here.

Learn more about our Scrum and Agile training sessions on WorldMindware.comPlease share!

The post Link: The Solution That Fits Our Team appeared first on Agile Advice.

Categories: Blogs

Hiring for Scrum: Agile vs Agility

Scrum Expert - Mon, 09/26/2016 - 17:19
The Manifesto for Agile Software Development says that you should prefer “Individuals and interactions over processes and tools”. But how do you hire the right people for your Scrum software development projects. In her article “Hiring for Agility – Mindset Matters in an Agile Organisation”, Nadia Smith suggests that you should look for more for Agility than Agile. The article starts by remembering the importance of hiring the right people. Nadia Smith wrote that “Agile refers to ‘the Practice’ as resume, education, certifications and experience, versus agility ‘the Mindset’ as attitude, skills, values and behaviours.” Agile vs Agility. Source: Then the article explains how culture should be the driving force behind the organization’s recruitment strategy. This recruitment process should abandon the traditional approach of scanning resume for skills and keywords and invest instead in assessing the attitude of the candidate. Nadia Smiths gives two examples of employee she hired on attitude and provides tips on how to assess the attitude of candidates. Her conclusion is that you should “Find people with a ‘can do’ attitude, who want to evolve, who show resilience, who embrace ambiguity, and have the desire to succeed. These people will evolve your Agile journey, enable growth and create success.” Read the full article on
Categories: Communities

Better Visibility Into Your Connected Work Items

We’re excited to bring to you a new view of connected cards, saving you time spent jumping...

The post Better Visibility Into Your Connected Work Items appeared first on Blog | LeanKit.

Categories: Companies

Thinking Differently About Agile Transformation: The “LeadingAgile Way”

Leading Agile - Mike Cottmeyer - Mon, 09/26/2016 - 15:00

Since coming onboard with LeadingAgile, I am continuously learning more about Agile Transformation and the market for our services.  Each day, I learn something new about why companies choose to work with us versus other consulting companies.  LeadingAgile is different and here is why…

The way businesses operate and survive in today’s market is constantly changing. Companies turn to Agile as a silver bullet, but it’s not. Tons of companies are trying and failing with Agile every day. They fail because they don’t see what it really takes to be successful. They have to start thinking differently about what it takes to adopt Agile in a systematic, meaningful, and lasting way.

To lead a successful Agile transformation, you have to address culture and practices, but it’s the underlying systems that support the Agile culture and practices that makes them meaningful.  All three are important, but where you begin the transformation is really the key! This is my main takeaway from my time so far and what makes our approach so fundamentally different.



Many executives believe if you cultivate an Agile culture, transformation will ooze through the company, and productivity will soar.  They believe if you focus on changing hearts and minds, the delivery systems will fall right into place.

If you have a complex organization, very rarely will a culture-driven transformation result in a true systematic change that sticks.


Even if key players throughout your organization attend Agile classes to adopt practices, there is still a huge missing piece to the puzzle.  Executives that start by changing practices expect the ripple effect to transform the company. Culture and systems are supposed to emerge by changing the way they work, but neither usually happens.  People go through the motions, but because the systems and the culture don’t support the practices, nothing really changes.

If these popular “start with practices” strategies work so well, why does Agile fail in so many companies that use them?

For your company to succeed, it’s time to think differently:  Systems are the key 

For permanent organizational change, adopting Agile is always about Systems first: forming teams, building backlogs, and regularly producing increments of working, tested software. Once you’ve rationalized the “system” and introduced solid Agile practices, a healthy, adaptive, and empowered culture will emerge over time.

At LeadingAgile, we believe you have to look at transformation through a different lens in order to make change really stick.  Culture, Practices, and Structures are all important, but where you choose to begin is essential. Here at LeadingAgile we believe organizations must start with systems, then teach practices, and guide culture over time for meaningful change to happen and for you to reach your business goals.

For more information about LeadingAgile transformation services, go to

The post Thinking Differently About Agile Transformation:
The “LeadingAgile Way”
appeared first on LeadingAgile.

Categories: Blogs

Sponsorship update

Agile Ottawa - Mon, 09/26/2016 - 14:43
We are very excited to say that we have some sponsors! They are Pyxis-technology as Premier MXI technologies as Platinum CIRA, and as Gold Having said that we still have some sponsorship opportunities. We are looking to fill … Continue reading →
Categories: Communities

4 Insights for an Agile Coach

Illustrated Agile - Len Lagestee - Mon, 09/26/2016 - 11:51

Earlier this year I started capturing a few insights needed to strengthen the impact of my coaching. It probably started around the New Year as many self-assessments do but it was when I was finishing up the 8 Ways to Measure Your Impact as an Agile Coach post in April that I realized just how much I was limiting myself. So I set out to put in the work I knew I needed to do.

Admittedly, this post has very little to do with Agile but more about how seemingly small personal changes begins to shape and influence the overall culture of an organization – one person at a time. If each person puts in just a little work, the results compound and the hard work of transforming to an Agile culture becomes that much easier.

So my hope is by revealing the areas I’m working on can trigger a few ideas for your own personal growth. Alright…take a deep breath. Let’s begin. (That was my self-talk by the way.)

Insight One: My Own Oxygen Mask. Before helping others, it is vital to find the areas keeping me from being an impactful coach. A sick coach can’t help anyone and the number one area keeping me from being a healthy and impactful coach was self-doubt.

I actually think this self-doubt is called “The Imposter Syndrome.” The feeling that no matter how much you have accomplished, you don’t deserve it. Whatever it is that causes one to question whether you are worthy, it was affecting me. It wasn’t crippling and didn’t keep me from pushing forward, but it was stealing my energy, draining my passion, and reducing my voice and message to a whisper.

Steven Pressfield in his seminal book “The War of Art” introduces “The Resistance” as the enemy to releasing our work into the world. Self-doubt is my Resistance. I would never want this doubt to be removed entirely. It keeps me on my toes and striving for improvement. One would think a person at my stage of life would have this one figured out by now…but I’m still working on it. Maybe you are too.

What I’m Doing: I have become dedicated to journal writing this year and I attempt to capture as much as I can remember about the events of the day. Especially the good things. Now, when those crazy doubts surface, I will scan through my journal, look back at those lives I’ve intersected with, have a little smile, get about removing the Resistance and “doing the work.”

Insight Two: Relationships. When I’m doubting myself there is a tendency to doubt others. When I am doubting others my ability to trust diminishes. When trust erodes there is no relationship. Without relationship, coaching becomes merely a business proposition. Just do the job.

We know coaching to deliver results are important but the human side is paramount. The role of a coach is to integrate what is necessary (catalyzing change, learning something new, instilling enthusiasm, growing capabilities) with what is beautiful (our humanness). The ONLY way to do this, in my opinion, is by building relationships first.

What I’m Doing: Increasing my attentiveness. I am trying to be intentional about toggling between leisurely and formal attentiveness throughout the day. Sometimes this will be spending more time to stop and have casual conversations or I will setup something more formal just to connect with people.

And yes, this will require me being more sacrificial of my time as mentioned in last weeks post. Always worth it as the result is often the development of long-term friendships even after our work together is complete.

Insight Three: Be prepared. The mission of a coach is to serve those who I come in contact with throughout the day. We often use the word “serve” loosely so what do I mean by “to serve”? In the context of coaching, my definition means to feed into the life of another human so they grow in capability (the skills they need), confidence (the energy they need) and joy (the purpose they need).

With the short amount of time I typically have within an organization, each interaction, each conversation, each ceremony and every person is crucial and should be treated as such. Without spending time to prepare myself I would too often feel like I was “winging it” most days. This could work some of the time but I found my coaching was scattered, would miss the mark, or would not trigger a change. While there will always be an element of randomness and chaos to what I do, a little more preparation would go a long way towards my mission.

What I’m Doing: Becoming much more intentional in blocking 15 minutes at the end of each day to reflect on the interactions and conversation I will likely have the next day. I will make notes in my calendar to capture key thoughts I’d like to communicate or model.

Periodically, I will think about all of the people I am currently working with and will capture those areas where I can support them in the areas of capability, confidence, and joy. Nancy Duarte, the author of the book “Resonate,” calls this knowing your audience.  This preparation allows me to focus my coaching and message and as a side benefit, reduce my level of self-doubt.

Insight Four: Amplification. With the “Resistance” of doubt diminished (but never removed), stronger relationships in place so we can have meaningful conversations about meaningful things, and having powerful interactions with those relationships through intentional preparation, there is a freedom to experiment and strengthen my words and behaviors.

What I’m Doing: Starting a podcast! Subscribe here. And who knows what else might be in the works!

Ultimately, amplification is about being braver and having courageous persistence. Using every moment as an opportunity to build strength into your ecosystem by communicating the right message, at the right time, to the right people, at the right volume. Every day I’m actively seeking ways to build on the previous day and ask myself if there are better ways for me to show up. More observations to capture in my journal!

From acceptance to amplification. Allowing myself a little grace so I can give more grace to others. Just a few ways I have grown recently but don’t worry, by next week I’m sure there will be something else to add to the list. That’s what I love about coaching and this journey we are on together. What insights are you discovering about the way you show up to work? Share your thoughts below.

Don’t forget…get the story behind this post at The Illustrated Agile Podcast.

Becoming a Catalyst - Scrum Master Edition

The post 4 Insights for an Agile Coach appeared first on Illustrated Agile.

Categories: Blogs

Toronto Agile Conference, Toronto, Canada, November 14 2016

Scrum Expert - Mon, 09/26/2016 - 09:15
Toronto Agile Conference is a one-day conference focused on Agile software development and Scrum project management. This popular conference has sold out each year and provides participants with numerous benefits with seven concurrent interactive sessions and plenty of opportunities to network. In the agenda of Toronto Agile Conference you can find topics like “How to get your whole team talking”, “Building powerful roadmaps”, “The Agile Ecosystem – Changing the way we think about Organizing to Deliver Value”, “Improve decisions using a value-focused prioritization framework”, “Moving from Technical Debt to Technical Health”, “Status and Power Improv”, “Build Your Own Value Stream Map with Lean”, “1000+ org agile transformation that nearly raced off a cliff”, “Refactoring Legacy Code”, “Culture for Great Teams and Results”, “Crushed by Technical Debt?”, “Reinventing Organizations for Agility”. Web site: Location for the Toronto Agile Conference conference: Hilton Toronto, 145 Richmond Street West, Toronto, Ontario M5H 2L2, Canada
Categories: Communities

Tampere Goes Agile, Tampere, Finland, November 5 2016

Scrum Expert - Mon, 09/26/2016 - 09:00
Tampere Goes Agile is a one-day conference that features Agile software development and Scrum project management expert speakers from Finland and abroad. In the agenda of Tampere Goes Agile you can find topics like “Experimenting Your Way Through Transformation”, “After Agile”, “Is Agile everything or is it the only thing?”, “Doctor, please fix my Agile!”, ” Pairing is sharing”, “When quality is just a cost: Useful approaches to testing”, “NoManagement – Change in self-organizing organization”, “Disciplined Agile Delivery for Critical System Development”. Web site: Location for the Tampere Goes Agile conference: Tampere Hall, Yliopistonkatu 55, Tampere, Finland
Categories: Communities

Announcement: REAL agility newsletter released today!

Learn more about transforming people, process and culture with the Real Agility Program

rachelheadshot“Each week there are more and more exciting items to share with our ever-increasing newsletter subscriber list of leaders who, like you, are creating positive change in organizations across Canada.”

Rachel Perry, Content & Community Coordinator

Recently we sent out a newsletter with some really great announcements! Here is a snippet from the weekly REALagility newsletter.

“Not only do BERTEIG coaches have fantastic insights to contribute to the advancement of the Agile industry, but also our Learning Events – for CSM, CSPO, CSD, SAFe, or Leadership – in both Toronto and Vancouver – continue to expand. In addition, multiple avenues for offering encouragement and support in a variety of ways are opening up all the time.

If our weekly newsletter were to include all the news, it would be 100 pages!

Sure, that might be a bit of an exaggeration but, truth-be-told, instead of putting EVERYTHING in the newsletter we share just key highlights, along with a warm invitation to hop on over to the Agile Advice blog where more knowledge, announcements and entertaining posts can give you plenty more details than what can be expressed in a weekly communication to your inbox.

We are excited to share that last month Agile Advice was viewed 18,000 times. Not only will you find more articles posted than ever before, but you will also discover a new development on the World Mindware page on Agile Advice; detailed accounts of hundreds of positive statements about BERTEIG’s coaches who are some of the leading Agile coaches in the world.

This week we featured Agile Leadership coach, Michael Sahota, onMichael Sahota - Profile Picture (2016) Agile Advice. In September, he will be presenting training for the Certified Agile Leadership (CAL1) training in Toronto. He was the second person to receive the designation to teach this class and the first to offer the training world-wide. He will also be offering a webinar this Wednesday, 24th Aug – register here.”

If you haven’t signed up for our weekly newsletter yet, I encourage you to consider giving it a try.

Learn more about our Scrum and Agile training sessions on WorldMindware.comPlease share!

The post Announcement: REAL agility newsletter released today! appeared first on Agile Advice.

Categories: Blogs

The Simple Leader: Oh the Humanity!

Evolving Excellence - Sun, 09/25/2016 - 10:02

This is an excerpt from The Simple Leader: Personal and Professional Leadership at the Nexus of Lean and Zen

When we treat people merely as they are, they will remain as they are. When we treat them as if they were what they should be, they will become what they should be.
– Thomas S. Monson

We’re supposedly all human, but sometimes we don’t act that way. Traditional leadership thinking has taught us that it is acceptable, sometimes even expected, for leaders to be harsh, uncaring, and distant. We may even believe that improving the bottom line means making choices such as putting the organization ahead of individuals.

Traditional business accounting skews our perspective to think of people only as costs. Nowhere on a profit and loss statement is the value of employee creativity, knowledge, and experience explicitly stated. This leads managers to make crazy decisions, like shedding thousands of years of experience in order to achieve a couple bucks an hour of labor cost savings.

Being a leader (instead of just a manager) means you should think differently. Human-centric leadership recognizes that your people are human and they should be valued accordingly. By understanding this, you can promote and get the most out the human side of your organization, your team, or even your family.

Categories: Blogs

Knowledge Sharing

SpiraTeam is a agile application lifecycle management (ALM) system designed specifically for methodologies such as scrum, XP and Kanban.