What are the hot topics the Pega Agile community are interested in from Agile2017?
Jessica Komerak, Brian Albere, and Tom Taylor (US-based Scrum Masters) are attending the Agile2017 conference this coming week. What items does our community want us to discover and bring back to Pega?
Pegasystems
US
Gaining an understanding of how enterprise organizations leverage agile best practices to speed customer implementations.
Rulesware
CA
I wish I could go. :(
How would you implement agile/Scrum when just learning Pega? Some tasks which with experience would take a couple of hours but being new to Pega could take anywhere from 4 hours to 3 days.
In reality, this scenario deals with any new product.
How does one deal with that? And try to maintain manageable and moving forward iterations.
Pegasystems Inc.
US
Great question... At the risk of being flippant, the classic joke for Agilists goes something like this:
"How many Agilists does it take to change a lightbulb?"
"It depends..."
One commonly used, if non-Scrum-purist, approach to kicking off new work is to hold a Sprint 0. Sprint 0 is essentially an iteration that's given to discovery and building out the approach when the team really starts sprinting. This is an opportunity to prep the product backlog - especially geared towards delivering value during the initial 2 first full sprints. It's also a time to take in some spikes - those investigational items that will give direction for the upcoming work, and potentially address architectural and infrastructure needs to support the project/feature.
Sprint 0's can be controversial as "potentially shippable product" isn't typically the end result, contrary to the goals of a Scrum iteration. While the intent of Sprint 0 may not yield shippable product, the deliverable is having both the work and the team in a ready-state and tee'd up for success.
Rulesware
CA
Hi Tom,
thank you for the response. I am in total agreement with your Sprint 0 positioning. I guess the part that I encountered/saw was the Sprint was a large number of Spikes and the relative "junior"-ness of the team meant that many "spikes" were never completed within a sprint and kept getting pushed. As mentioned previously, the problem was there was not enough knowledge to get estimates anywhere close to a valid estimate and that caused problems itself. It's a long discussion where it turns it out , it might have been more of a symptom of a problem and not the actual problem itself... This might require an actual conversation instead of the back and forth and then a lessons learned blog posting, perhaps... ??
Enjoy the conference.
Pegasystems Inc.
US
I would love to hear stories about how organizations have moved to CI/CD and the successes and failures they experienced along the way.
Infosys
IN
WIth growing acceptance of in big transformation programs, size of projects is growing. Percentage of Pega projects being run in global delivery model is at all time high.
Considering this, I would like to certainly hear about scaling agile.