This comparison is different, coming from the point of view of a WordPress specialist.
JIRA vs Trello vs Asana vs TeamClerk vs WordPress: Conclusion
JIRA: Use it when working with a team on larger software projects, and if you’re utilizing things like scrum for managing your work.
Trello: Use it if you’re looking for a tool that you and your team can use for free, and that gives you ultimate freedom to manage your projects however you wish.
Asana: Use it if you expect your project management tool to introduce some structure into your workflow, and if you prefer list-based tools, rather than card-based.
TeamClerk: Use it to track your progress in real-time, and to get a good overview of a handful of projects running in parallel from the same dashboard.
Managing projects with WordPress + plugins: Not really.
Author = Karol K (codeinwp)
Zombies: (…) they are here, and their number is growing rapidly. Mindless, drooling herds of developers, testers, designers and others moaning ‘chaaaange’ and shambling around the building to all sorts of brainless Scrum-activities.
Symptoms of Zombie Scrum
Symptom #1: No beating heart
Symptom #2: No (desire for) contact with the outside world
Symptom #3: No emotional response to success or failure
Symptom #4: No drive to improve
Causes of Zombie Scrum
Cause #1: A bit too homegrown, or ‘Cargo Cult Scrum’
Cause #2: No urgency
Cause #3: Competing Values
Treating Zombie Scrum
Treatment #1: Become a Zombie-whisperer
Treatment #2: Introduce Healthy Scrum into the population
Treatment #3: Shake things up (don’t continue the stumble)
Treatment #4: Involve the broader Scrum Community
Author = Christiaan Verwijs
Is your team suffering from Zombie Scrum? And if so, what can you do to improve? Do you wonder how other teams work with Scrum? How many members they have? What the usual length of a Sprint is? Is Scrum really helping teams deliver value to stakeholders faster and making them happier as a result? Find out with the first version of the Free Zombie Scrum Symptoms Checker.
The mission of our app “Our mission with this app is to use an empirical approach to better understand how teams and organizations work with Scrum, what it makes possible for them, what enables or impedes their success and how to better support them.“
Based on a scientific approach
Receive your team’s profile
Open-source data and replication
Next steps for our research
Give it a try!
Author = Christiaan Verwijs (Scrum.org)
Fight Zombie Scrum!
Link to the Free Online Tool to Diagnose your team
Author = The Liberators
I’m not a fan of measuring velocity. Velocity is a point-in-time measure of capacity. That means that when things change for the team or in the code, the velocity often changes. (See Velocity is Not Acceleration.)
Instead, I like to measure cycle time. Cycle time is the entire time it takes a team to finish something on their board.
Cycle time indicates how much the team collaborates together and how small the stories are. We want more collaboration and smaller stories in any agile approach. That’s why measuring cycle time creates a virtuous (positive) feedback loop.
Here’s how to measure cycle time: I like to use a value stream map to see the wait times and work times.
Note every time the work changes state: is it a work time (above the line) or a wait time (below the line)
Add all the work times together.
Add all the wait times together.
Cycle time is all the work time plus all the wait time.
Map the Value Stream for a Collaborative Team
Map the Value Stream for a Team Where People Work as Individuals
Use Cycle Time to Estimate Story Duration
Author = Johanna (Rothman Consulting Group, Inc.)
Sprint Review Meeting
The Sprint review meeting should include the following:
Attendance and participation of the Scrum Team, product owner, and invited key stakeholders.
The Product Owner should report the items in the Product Backlog; what backlog items have been done and what have not.
The development team discusses what went well and the problems they experienced. They should also inform the group what they did to resolve the problems.
The development team demonstrates their completed work while answering questions about their increment.
The product owner leads the discussion on the Product Backlog as it currently stands. They set projected completion dates based on the progress of the Sprint session.
To give valuable input to the Sprint planning, the entire group establishes the next steps during the Sprint review meeting.
This is a time to review potential changes in the marketplace, the valuation of the project and what areas are considering to be the most valuable. The next steps should also be outlined.
Review the timeline, budget, potential capabilities, and marketplace to determine the next anticipated product release.
By the end of the Sprint Review, revisions should be made to the Product Backlog to better define probable backlog items for the next Sprint session. The Product Backlog can be adjusted completely to introduce new opportunities.
Focus on the End User
Involve the Product Owner
Understand Group Dynamics
Author = Luís Gonçalves
Always interesting to read a pro/con analysis between Waterfall & Agile methodologies.
It is easy to understand and manage as stages are clearly defined.
Meticulous record keeping and documentation.
Client knows what to expect. Client will have an idea of the size, cost and timeline for the project. The client will have a definite idea of what their product will do in the end.
In the case of employee turnover, waterfall’s strong documentation allows for minimal project impact
It often becomes rigid and resistant to change.
It relies heavily on initial requirements. However if these requirements are faulty in any manner, the project is doomed.
The whole product is only tested at the end. If errors are discovered late in the process, their existence may have affected the rest of the project.
The plan does not take into account a client’s evolving needs throughout the project cycle.
It allows for changes to be made after the initial planning stage. It follows client’s requirements changes.
It is easier to add features that will keep the product up to date with the latest developments in the industry.
At the end of each sprint, project priorities are evaluated. This allows clients to add their feedback, so that they ultimately get the product they desire.
The testing at the end of each sprint ensures that the errors are caught in each cycle.
This dynamic methodology is not suitable for processes that require a complex decision making of formal planning such as construction, manufacturing, military, health care system among others.
As the initial project does not have a definitive plan, the final product can be grossly different that what was initially intended.
Author = Liz Parody (Moove-it, via Medium)
SEUs follow a 1:1 ratio, where one hour of participation or preparation is equal to one SEU.
Categories = There are four (4) categories you can choose from when selecting SEUs
Page covers Renewal Requirements and includes answers to the following FAQs:
How is the value of an SEU calculated?
How do I get SEUs?
I do a lot of training and coaching. Which SEU category does this fit into?
How many SEUs will I need to maintain my CSP certification?
I am logging SEUs to renew. How recent do they have to be?
When logging SEUs, what information do I need to include or how detailed do I need to be?
Author = ScrumAlliance
Author = ScrumAlliance
They are not the same. Article covers:
TDD = Test-driven development = a technique of using automated unit tests to drive the design of software and force decoupling of dependencies.
ATDD = Acceptance Test Driven Development,
aka STDD = Storytest Driven Development = a technique used to bring customers into the test design process before coding has begun. It is a collaborative practice where users, testers, and developers define automated acceptance criteria.
BDD = Behavior-Driven Development = combines the general techniques and principles of TDD with ideas from domain-driven design. BDD is a design activity where you build pieces of functionality incrementally guided by the expected behavior.
Article also discusses Differences.
Author = Gabo Esquivel
Scrum master, project manager interview questions shared by candidates.
Author = Various (Glassdoor)
Article – With agile fast becoming standard practice at most companies, scrum masters are in great demand. Here is a look at the Scrum Master role, relevant certifications, expected salaries and career opportunities.
Author = Moira Alexander (CIO)